Account Analysis for Contra Account Report

General Ledger◆ Seeded · Account analysis

Prints balances by account segment and a secondary segment, listing the contra account for each journal entry and the subledger document number for imported transactions, filtered by date, flexfield, contra account, and amount range.

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 Account Analysis for Contra Account 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

1,420

Accounts

48,000

Lines

380

No contra

Account	Contra Account	Journal	Document	Debit	Credit
1000-2100-000	1000-2100-000	Sample	Sample	$1,240,500.00	$1,240,500.00
1000-5400-000	1000-5400-000	—	—	$842,150.75	$842,150.75
1000-1410-000	1000-1410-000	Sample	Sample	$96,400.00	$96,400.00
2000-2100-000	2000-2100-000	—	—	$1,005,233.10	$1,005,233.10
1000-6300-000	1000-6300-000	Sample	Sample	$58,720.40	$58,720.40
1000-2100-000	1000-2100-000	Sample	Sample	$1,240,500.00	$1,240,500.00

AI Analyst · active

reading

The report pairs each journal line with its contra account.

flag

380 lines have no resolvable contra account — multi-line journals where the offset can't be paired one-to-one.

root cause & next step

Contra pairing is only clean on two-line journals; the build derives a contra dimension that holds on complex journals too.

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
GL_CODE_COMBINATIONS	dimension	dimension
GL_BALANCES	dimension	dimension
Debit	measure	measure
Credit	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_JE_LINES	26	2
GL_CODE_COMBINATIONS	7	61
GL_BALANCES	Setup / 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 Contra-account pairing is rarely configured cleanly out of the box; the common build adds a derived contra dimension and exposes it as a reusable subject area. Irvine rebuilds these on your data.