Document Number Audit Report

Receivables◆ Seeded · Receivables balances

Lists document numbers assigned to transactions, adjustments, and receipts to surface gaps in a sequence, with the status, customer, currency, and amount of each, by sequence name and number range.

Sample build of the Document Number Audit 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

Sequences

18,400

Documents

Gaps

Document Type	Sequence	First	Last	Gaps	Status
Standard	Sample	Sample	Sample	Sample	Open
Corporate	—	—	—	—	Posted
Standard	Sample	Sample	Sample	Sample	Validated
Default	—	—	—	—	Open
Standard	Sample	Sample	Sample	Sample	Paid
Standard	Sample	Sample	Sample	Sample	Open

AI Analyst · active

reading

The report lists assigned document numbers to surface gaps in a sequence.

flag

12 gaps across the sequences — either deleted documents or a numbering setup issue, which several jurisdictions prohibit for tax documents.

root cause & next step

Explain each gap (voided versus missing); a gap in a statutory document sequence is a compliance finding.

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
AR_CASH_RECEIPTS_ALL	dimension	dimension
AR_ADJUSTMENTS_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.

Receivables 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
RA_CUSTOMER_TRX_ALL	58	16
AR_CASH_RECEIPTS_ALL	25	9
AR_ADJUSTMENTS_ALL	19	2

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 Sequence-gap detection is statutory in many countries; localization adds the legally required numbering and an exception alert. Irvine rebuilds these on your data.