Analytics Catalog/Oracle Fusion ERP/General Ledger/Average Balance Audit Account Analysis Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Seeded report · Account analysis

Average Balance Audit Account Analysis Report

General Ledger◆ Seeded · Account analysis

Displays the detail account activity behind aggregate and average balances, showing daily average balance information for selected accounts over a date range, with as-of date and average-balance-type parameters.

Run note · BIP run  High-volume GL extracts can exceed BI Publisher's online output limit and time out. Run it as a scheduled process (ESS) with output bursted to file or email rather than online preview, and bound it by ledger and period.

Sample build of the Average Balance Audit Account Analysis Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Average Balance Audit Account Analysis Report
Sample build · illustrative
Filters
Period
FEB-26
Ledger
US Primary
Currency
USD
240
Accounts
$42.00M
Avg balance
12
No daily balances
AccountAs-of DatePeriod AvgQtd AvgYtd AvgEnding Bal
1000-2100-0002026-04-30APR-26SampleSampleSample
1000-5400-0002026-03-31MAR-26
1000-1410-0002026-02-28FEB-26SampleSampleSample
2000-2100-0002026-01-31JAN-26
1000-6300-0002025-12-31DEC-25SampleSampleSample
1000-2100-0002026-04-30APR-26SampleSampleSample
AI Analyst · active
reading

The report shows the daily average balances behind the aggregate balances.

flag

12 accounts have no daily balances — average daily balances isn't enabled for their ledger, so the averages come back blank.

root cause & next step

Enable average balance processing for those ledgers; without the daily balance store the report can't compute an average.

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.

GL_CODE_COMBINATIONSdimensionGL_DAILY_BALANCESdimensionGL_BALANCESfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
GL_CODE_COMBINATIONSdimensiondimension
GL_DAILY_BALANCESdimensiondimension
Amountmeasuremeasure
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.
General Ledger 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.

TableReporting columnsSubject areas
GL_BALANCESSetup / configuration table — joined for reference, not exposed for analytics
GL_CODE_COMBINATIONS761
GL_DAILY_BALANCESSetup / configuration table — joined for reference, not exposed for analytics
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  Only meaningful with average daily balances enabled; most customers want it re-cut as a trend visual rather than the seeded audit listing. Irvine rebuilds these on your data.