Payables Period Close Exceptions Report

Payables◆ Seeded · Period close

Lists exceptions that prevent the Payables accounting period from closing.

Related The Payables-specific companion to the flagship Subledger Period Close Exceptions report.

Run note · Performance The subledger (XLA) join — especially Projects-to-XLA — is a known BI Publisher performance trap on large ledgers. Pre-join it in the warehouse, or apply tight ledger, period, and source filters before running online.

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

Payables Period Close Exceptions Report

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

Open exceptions

$1.40M

Unaccounted value

Blocking close

Exception Type	Invoice/payment	Supplier	Amount	Status
Standard	Sample	Acme Industrial	$1,240,500.00	Open
Corporate	—	Northwind Trading	$842,150.75	Posted
Standard	Sample	Globex Holdings	$96,400.00	Validated
Default	—	Initech LLC	$1,005,233.10	Open
Standard	Sample	Umbrella Corp	$58,720.40	Paid
Standard	Sample	Acme Industrial	$1,240,500.00	Open

AI Analyst · active

reading

The report lists the exceptions that prevent the Payables period from closing — unaccounted, unvalidated, or held items.

flag

18 exceptions are hard blockers worth $1.4M — the period can't close until they clear.

root cause & next step

Clear blockers by type (validate, account, or sweep); the period-close exceptions list is the close critical path.

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

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_PAYMENTS_ALL	dimension	dimension
XLA_AE_HEADERS	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_ALL	63	15
AP_INVOICE_PAYMENTS_ALL	22	2
XLA_AE_HEADERS	16	19

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 The seeded list is the close blocker; the build turns it into an owner-assigned close-readiness worklist. Irvine rebuilds these on your data.