Accounting Hub Journal Entry Line Extract
The journal entry lines the Accounting Hub creates from external source systems — each line's account, entered and accounted amounts, source transaction, and event type — the single extract that carries third-party subledger accounting into your GL and warehouse. One pattern serves every source system.
Related One extract replaces the per-source-system variants — it serves every Accounting Hub source on a single, parameter-driven pattern.
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 Accounting Hub Journal Entry Line Extract — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.
| Source System | Event Type | Account | Entered Debit | Entered Credit | Accounted Amount | Accounting Date |
|---|---|---|---|---|---|---|
| Sample | Standard | 1000-2100-000 | $1,240,500.00 | $1,240,500.00 | $1,240,500.00 | 2026-04-30 |
| — | Corporate | 1000-5400-000 | $842,150.75 | $842,150.75 | $842,150.75 | 2026-03-31 |
| Sample | Standard | 1000-1410-000 | $96,400.00 | $96,400.00 | $96,400.00 | 2026-02-28 |
| — | Default | 2000-2100-000 | $1,005,233.10 | $1,005,233.10 | $1,005,233.10 | 2026-01-31 |
| Sample | Standard | 1000-6300-000 | $58,720.40 | $58,720.40 | $58,720.40 | 2025-12-31 |
| Sample | Standard | 1000-2100-000 | $1,240,500.00 | $1,240,500.00 | $1,240,500.00 | 2026-04-30 |
The extract reads XLA_AE_LINES with its headers and transaction entities, returning every accounted line the Accounting Hub generated from external sources, tagged by source system and event type.
One source system's lines are accounted but not yet transferred to GL — its load finished after the daily Transfer to GL ran, so its entries lag a cycle.
Sequence each source system's load before the GL transfer, or run an extra transfer after a late load; this is the usual cause of an Accounting-Hub-to-GL timing gap.
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
- XLA_AE_HEADERS
- XLA_AE_LINES
- XLA_TRANSACTION_ENTITIES
- XLA_TRANSACTION_HEADERS
- XLA_SUBLEDGERS
- GL_LEDGERS
- GL_CODE_COMBINATIONS
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.
| Element | Type | Definition |
|---|---|---|
| XLA_AE_LINES | dimension | dimension |
| XLA_TRANSACTION_ENTITIES | dimension | dimension |
| XLA_TRANSACTION_HEADERS | dimension | dimension |
| XLA_SUBLEDGERS | dimension | dimension |
| Entered Debit | measure | measure |
| Entered Credit | measure | measure |
| Accounted Amount | measure | measure |
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 |
|---|---|---|
| XLA_AE_HEADERS | 16 | 19 |
| XLA_AE_LINES | 23 | 17 |
| XLA_TRANSACTION_ENTITIES | 2 | 3 |
| XLA_TRANSACTION_HEADERS | Setup / configuration table — joined for reference, not exposed for analytics | |
| XLA_SUBLEDGERS | Setup / configuration table — joined for reference, not exposed for analytics | |
| GL_LEDGERS | 10 | 104 |
| GL_CODE_COMBINATIONS | 7 | 61 |