Journal and Transaction Details Report

General Ledger◆ Seeded · Journals

Lists general ledger journals and subledger transaction activity with header, line, and distribution-level detail, including the account combinations on each line; runs only from Oracle Analytics Publisher.

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.

Run note · Performance The subledger (XLA) join — especially Projects-to-XLA — is a known BI Publisher performance trap on large ledgers. Pre-join it in the warehouse, or apply tight ledger, period, and source filters before running online.

Sample build of the Journal and Transaction Details Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Journal and Transaction Details Report

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

1,420

Accounts

210,000

Lines

$0 diff

Ties to subledger

Account	Gl Journal	Subledger Doc	Entered Debit	Entered Credit	Source
1000-2100-000	Sample	US Primary	$1,240,500.00	$1,240,500.00	Sample
1000-5400-000	—	EU Primary	$842,150.75	$842,150.75	—
1000-1410-000	Sample	US Primary	$96,400.00	$96,400.00	Sample
2000-2100-000	—	UK Primary	$1,005,233.10	$1,005,233.10	—
1000-6300-000	Sample	US Primary	$58,720.40	$58,720.40	Sample
1000-2100-000	Sample	US Primary	$1,240,500.00	$1,240,500.00	Sample

AI Analyst · active

reading

The report lists GL journals with their subledger transaction detail and account combinations.

flag

The seeded version runs only in BI Publisher and is slow at this volume — 210K lines time out interactively.

root cause & next step

Push the GL-to-subledger join into the warehouse with pre-joined lineage so the same drill is instant.

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
XLA_AE_LINES	dimension	dimension
XLA_AE_HEADERS	dimension	dimension
GL_CODE_COMBINATIONS	dimension	dimension
Entered Debit	measure	measure
Entered 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
XLA_AE_LINES	23	17
XLA_AE_HEADERS	16	19
GL_CODE_COMBINATIONS	7	61

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 The seeded BIP-only report is slow on volume; the common build pushes the GL-to-subledger join into the warehouse with pre-joined lineage. Irvine rebuilds these on your data.