Analytics Catalog/Oracle Fusion ERP/General Ledger/Oracle Fusion GL Trial Balance Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · General Ledger (GL)

Oracle Fusion GL Trial Balance Report

General Ledger

A trial balance for Oracle Fusion — every account's debit and credit balance by ledger as of a date, the starting point for the close and the tie-out to the financial statements.

What the seeded report gives you

Trial Balance Report · OTBI subject area "General Ledger – Balances Real Time". Columns: Ledger, Period, Account, Beginning/Period Dr/Cr/Ending Balance, Currency, Balance Type.

Where it falls short

What finance actually needs

Related  Same trial-balance question as the flagship General Ledger Trial Balance Report — this is the 'Oracle Fusion GL Trial Balance' name people search for.

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

Oracle Fusion GL Trial Balance Report
Sample build · illustrative
Filters
Ledger
US Primary
Period
JAN-2026
Currency
USD
Basis
Actual
1,420
Accounts
$0 diff
In balance
3
Ledgers
AccountDescriptionBegin BalancePeriod DebitPeriod CreditEnd Balance
1100-000Cash – Operating4,210,5001,880,0001,640,2504,450,250
1210-000Accounts Receivable8,640,2003,920,0002,510,40010,049,800
1500-000Fixed Assets – Cost22,310,000540,000022,850,000
2100-000Accounts Payable(5,120,300)1,210,0002,360,000(6,270,300)
4000-000Revenue(14,800,000)04,310,000(19,110,000)
5000-000Cost of Goods Sold9,210,0002,640,000011,850,000
Total10,820,65010,820,650
AI Analyst · active
reading

The report reads GL_BALANCES by account and ledger as of the selected date.

flag

Total debits equal credits, but one suspense account carries a non-zero balance that should clear before close.

root cause & next step

Clear the suspense balance to its proper account; a trial balance that ties overall can still hide a suspense balance that fails the statements.

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.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
SELECT  cc.concatenated_segments AS account, cc.account_description,
        b.begin_balance_dr - b.begin_balance_cr AS beginning_balance,
        b.period_net_dr AS period_debits, b.period_net_cr AS period_credits,
        (b.begin_balance_dr - b.begin_balance_cr) + b.period_net_dr - b.period_net_cr AS ending_balance
FROM    gl_balances b
JOIN    gl_code_combinations cc ON cc.code_combination_id = b.code_combination_id
WHERE   b.ledger_id = :ledger_id AND b.period_name = :period_name
  AND   b.currency_code = :reporting_currency AND b.actual_flag = 'A'
ORDER BY cc.concatenated_segments;
:ledger_id :period_name :reporting_currency

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 account / ledger / period.

dim_accountsegment combinationdim_ledgerledger contextdim_periodaccounting calendarfct_gl_balancesfact · one row per account / ledger / pe…beginning_balance · period_activity…
●— fact → dimension join
ElementTypeDefinition
dim_accountdimensionsegment combination
dim_ledgerdimensionledger context
dim_perioddimensionaccounting calendar
beginning_balancemeasureopening
period_activitymeasureDr/Cr net
ending_balancemeasureclosing
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.

TableReporting columnsSubject areas
GL_BALANCESSetup / configuration table — joined for reference, not exposed for analytics
GL_CODE_COMBINATIONS761
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.

The same question across systems.

ConceptOracle FusionSAP S/4HANAWorkday
ReportTrial Balance ReportTrial balance (S_ALR / ACDOCA)Trial Balance report
Balance sourceGL_BALANCESACDOCALedger account object
AccountGL_CODE_COMBINATIONSSKA1 / SKB1Ledger account
ExtractionBICCCDS / ODataRaaS / Prism