Subledger Period Close Exceptions Report
The Subledger Period Close Exceptions Report lists transactions across all subledgers that are not fully accounted, transferred, or posted — the exact items that stop a period from closing. Running it early in close turns a frantic hunt into a checklist.
The question it answers
What is still blocking the close, and in which subledger does each exception sit?
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 Subledger Period Close Exceptions Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.
| Subledger | Event | Transaction | Status | Accounted | Amount |
|---|---|---|---|---|---|
| US Primary | Sample | Sample | Open | 1000-2100-000 | $1,240,500.00 |
| EU Primary | — | — | Posted | 1000-5400-000 | $842,150.75 |
| US Primary | Sample | Sample | Validated | 1000-1410-000 | $96,400.00 |
| UK Primary | — | — | Open | 2000-2100-000 | $1,005,233.10 |
| US Primary | Sample | Sample | Paid | 1000-6300-000 | $58,720.40 |
| US Primary | Sample | Sample | Open | 1000-2100-000 | $1,240,500.00 |
Each row is a transaction that has not completed its accounting lifecycle. Group by subledger and status to see exactly what each module owes the close.
37 exceptions, 21 of them unaccounted in Payables — the largest single block to closing the period on schedule.
Traced to XLA_EVENTS in the No Action / Error state: run Create Accounting in final mode for Payables, clear the errors, then transfer and post. Re-run until the count is zero.
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
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.
| Element | Type | Definition |
|---|---|---|
| XLA_EVENTS | dimension | dimension |
| XLA_TRANSACTION_ENTITIES | dimension | dimension |
| GL_PERIOD_STATUSES | dimension | dimension |
| Amount | measure | measure |
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 |
|---|---|---|
| XLA_AE_HEADERS | 16 | 19 |
| XLA_EVENTS | 3 | 1 |
| XLA_TRANSACTION_ENTITIES | 2 | 3 |
| GL_PERIOD_STATUSES | 11 | 1 |