Journals Report

General Ledger◆ Seeded · Journals

Provides journal activity for a period or range of periods by balancing segment, currency, and account range, printing accounting date, category, journal name, entered debits and credits, and account totals.

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

Journals Report

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

8,400

Journals

8,210

Posted

190

Unposted

Journal	Category	Source	Entered Debit	Entered Credit	Status
Sample	Computer-Hardware	Sample	$1,240,500.00	$1,240,500.00	Open
—	Buildings	—	$842,150.75	$842,150.75	Posted
Sample	Vehicles	Sample	$96,400.00	$96,400.00	Validated
—	Furniture-Fixtures	—	$1,005,233.10	$1,005,233.10	Open
Sample	Machinery	Sample	$58,720.40	$58,720.40	Paid
Sample	Computer-Hardware	Sample	$1,240,500.00	$1,240,500.00	Open

AI Analyst · active

reading

The report lists journal activity by balancing segment, currency, and account range.

flag

190 journals are entered but unposted at the period cut, so their amounts aren't in the balances yet.

root cause & next step

Post or document the unposted journals before close; an unposted journal is a number missing from the trial balance.

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
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
GL_JE_HEADERS	34	2
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 layout is dense and print-oriented; teams typically rebuild it as a filterable journal explorer with source/category facets and Excel export. Irvine rebuilds these on your data.