GL Balance Tracking for Contracts Report

General Ledger

Tracks general-ledger balances for a revenue stream by cost center, channel, and currency over time — a movement view that follows specific account combinations period over period.

Related A focused balance-tracking view; the General Ledger Trial Balance Monthly Movements Report applies the same movement logic across all accounts.

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 GL Balance Tracking for Contracts Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

GL Balance Tracking for Contracts Report

Sample build · illustrative

Filters

Account From

1000-1410-000

Account To

1000-1410-000

Product Line From

Sample

Product Line To

Sample

Contract

Sample

Conversion Type

Standard

240

Account combos

$18.40M

Tracked balance

Periods

Account Combination	Cost Center	Channel	Currency	Period	Balance
1000-2100-000	$1,240,500.00	Standard	USD	APR-26	$1,240,500.00
1000-5400-000	$842,150.75	Corporate	USD	MAR-26	$842,150.75
1000-1410-000	$96,400.00	Standard	USD	FEB-26	$96,400.00
2000-2100-000	$1,005,233.10	Default	USD	JAN-26	$1,005,233.10
1000-6300-000	$58,720.40	Standard	USD	DEC-25	$58,720.40
1000-2100-000	$1,240,500.00	Standard	USD	APR-26	$1,240,500.00

AI Analyst · active

reading

The report reads GL_BALANCES on the selected account combinations and trends them by cost center and channel.

flag

One cost center's balance swings sharply month to month — a reclassification churn that nets out but distorts any single-month read.

root cause & next step

Trace the churn to a recurring reclass; if a manual reclass repeats every month, fix the original coding so the balance is right at source.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

The SQL behind this report is not published. Its logic is one organisation's own setup, so it would not run anywhere else. The tables it reads are listed below, and the warehouse model shows how the same data lands in your warehouse.

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 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
GL_CODE_COMBINATIONS	dimension	dimension
GL_DAILY_RATES	dimension	dimension
GL_LEDGERS	dimension	dimension
Cost Center	measure	measure
Balance	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.

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.

Table	Reporting columns	Subject areas
GL_BALANCES	No page in this catalog’s data dictionary yet
GL_CODE_COMBINATIONS	7	61
GL_DAILY_RATES	1	10
GL_LEDGERS	10	104

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.