Payables Payment Requests Import Report

Payables◆ Seeded · Payments

Lists payment requests for invoices that are imported, or rejected with rejection reasons.

Sample build of the Payables Payment Requests Import Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

1,840

Requests

Rejected

$420K

Held value

Source	Payment Request	Supplier	Amount	Status	Reject Reason
Sample	Sample	Acme Industrial	$1,240,500.00	Open	Standard
—	—	Northwind Trading	$842,150.75	Posted	Corporate
Sample	Sample	Globex Holdings	$96,400.00	Validated	Standard
—	—	Initech LLC	$1,005,233.10	Open	Default
Sample	Sample	Umbrella Corp	$58,720.40	Paid	Standard
Sample	Sample	Acme Industrial	$1,240,500.00	Open	Standard

AI Analyst · active

reading

The report lists imported payment requests and those rejected with reasons.

flag

42 payment requests were rejected, holding $420K of expense and one-time payments before they become payable.

root cause & next step

Fix the rejection reasons — usually supplier, bank, or party setup; a rejected payment request is a payment someone is waiting on.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

AP_INVOICES_INTERFACE
IBY_PAYMENTS_ALL
AP_INVOICES_ALL

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.

The SQL data set is authored to this report's exact spec during the build and ships as the BI Publisher data model plus a matching dbt model — one definition, both layers.

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

●— fact → dimension join

Element	Type	Definition
IBY_PAYMENTS_ALL	dimension	dimension
AP_INVOICES_ALL	dimension	dimension
Amount	measure	measure

Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.

How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →

See the complete model

How this report's fact and dimensions fit the full picture, via conformed keys.

Payables data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

Table	Reporting columns	Subject areas
AP_INVOICES_INTERFACE	Setup / configuration table — joined for reference, not exposed for analytics
IBY_PAYMENTS_ALL	Setup / configuration table — joined for reference, not exposed for analytics
AP_INVOICES_ALL	63	15

Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.

Customization note Re-pointed to auto-triage rejected payment requests by reason. Irvine rebuilds these on your data.