General Ledger Account Details Report

General Ledger◆ Seeded · Account analysis

Provides journal information to trace each transaction back to its original source, printing a separate page per balancing segment with the account affected, line amount, and beginning and ending balances.

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 General Ledger Account Details Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Ledger

US Primary

Account

5200-300 Travel

Period

JAN-2026

1,420

Accounts

48,000

Lines

$0 diff

In balance

Date	Journal	Source	Description	Debit	Credit	Balance
01-JAN-26	—	—	Opening balance			8,200
05-JAN-26	JE-10231	Payables	Invoice INV-88231	12,400		20,600
18-JAN-26	JE-10455	Manual	Reclass to project		3,000	17,600
22-JAN-26	JE-10502	Payables	Invoice INV-88455	7,850		25,450
			Period movement	20,250	3,000	25,450

AI Analyst · active

reading

The report prints journal detail per account so each line traces to its source.

flag

A set of lines on the manual journal source carry no description or reference — they can't be traced back to a document.

root cause & next step

Require a description and reference on manual journals; a line you can't trace is the one auditors ask about first.

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_JE_HEADERS	dimension	dimension
GL_CODE_COMBINATIONS	dimension	dimension
GL_BALANCES	dimension	dimension
Line 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.

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_JE_HEADERS	34	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 Ships as a fixed PDF ordered by account segment; controllers usually rebuild it with drill-through from balance to journal line and a pivot by cost center or management hierarchy. Irvine rebuilds these on your data.