Import Payables Invoices Report

Payables◆ Seeded · Invoices

Reports the results of the process that creates Payables invoices from data in the open interface tables.

Sample build of the Import Payables Invoices 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

8,200

Lines imported

160

Rejected

$1.10M

Held value

Batch	Source	Imported	Rejected	Amount	Error Reason
Sample	Sample	Sample	Sample	$1,240,500.00	Standard
—	—	—	—	$842,150.75	Corporate
Sample	Sample	Sample	Sample	$96,400.00	Standard
—	—	—	—	$1,005,233.10	Default
Sample	Sample	Sample	Sample	$58,720.40	Standard
Sample	Sample	Sample	Sample	$1,240,500.00	Standard

AI Analyst · active

reading

The report reports the process that creates Payables invoices from the open interface.

flag

160 lines were rejected, holding $1.1M of supplier invoices in the interface, not yet liabilities.

root cause & next step

Fix the interface errors — often supplier site, distribution, or tax setup; a rejected import line is a bill not yet on the books.

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
AP_INVOICE_LINES_INTERFACE
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
AP_INVOICE_LINES_INTERFACE	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
AP_INVOICE_LINES_INTERFACE	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 at the interface to QA and auto-correct rejected rows before import rather than reading rejections after the fact. Irvine rebuilds these on your data.