Oracle Fusion GL Trial Balance Report
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
- Account-balance level only — no inline drill to the journal lines that built the balance.
- One ledger at a time; no native consolidated trial balance with eliminations.
- No prior-period or budget variance columns next to the balance.
- Limited segment pivoting; export caps; no retained history for trend.
What finance actually needs
- Drill: ending balance → journal line → subledger transaction → source document.
- Multi-ledger consolidated trial balance in one reporting currency.
- Prior-period, prior-year, and budget variance columns with % movement.
- Pivot by entity, cost center, or natural account without re-running.
- Reconciliation status + materiality flags; nightly snapshot reconciled to source.
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.
| Account | Description | Begin Balance | Period Debit | Period Credit | End Balance |
|---|---|---|---|---|---|
| 1100-000 | Cash – Operating | 4,210,500 | 1,880,000 | 1,640,250 | 4,450,250 |
| 1210-000 | Accounts Receivable | 8,640,200 | 3,920,000 | 2,510,400 | 10,049,800 |
| 1500-000 | Fixed Assets – Cost | 22,310,000 | 540,000 | 0 | 22,850,000 |
| 2100-000 | Accounts Payable | (5,120,300) | 1,210,000 | 2,360,000 | (6,270,300) |
| 4000-000 | Revenue | (14,800,000) | 0 | 4,310,000 | (19,110,000) |
| 5000-000 | Cost of Goods Sold | 9,210,000 | 2,640,000 | 0 | 11,850,000 |
| Total | 10,820,650 | 10,820,650 |
The report reads GL_BALANCES by account and ledger as of the selected date.
Total debits equal credits, but one suspense account carries a non-zero balance that should clear before close.
Clear the suspense balance to its proper account; a trial balance that ties overall can still hide a suspense balance that fails the statements.
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
- GL_BALANCES
- GL_CODE_COMBINATIONS
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;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.
| Element | Type | Definition |
|---|---|---|
| dim_account | dimension | segment combination |
| dim_ledger | dimension | ledger context |
| dim_period | dimension | accounting calendar |
| beginning_balance | measure | opening |
| period_activity | measure | Dr/Cr net |
| ending_balance | measure | closing |
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_BALANCES | Setup / configuration table — joined for reference, not exposed for analytics | |
| GL_CODE_COMBINATIONS | 7 | 61 |
The same question across systems.
| Concept | Oracle Fusion | SAP S/4HANA | Workday |
|---|---|---|---|
| Report | Trial Balance Report | Trial balance (S_ALR / ACDOCA) | Trial Balance report |
| Balance source | GL_BALANCES | ACDOCA | Ledger account object |
| Account | GL_CODE_COMBINATIONS | SKA1 / SKB1 | Ledger account |
| Extraction | BICC | CDS / OData | RaaS / Prism |