GL_JE_LINES
Product: GLtransactionLedger-striped (LEDGER_ID)General ledger journal lines — the debit/credit grain: one row per line with the account combination, entered and accounted amounts, effective date, and the drill-back link to subledger accounting
Amounts come in pairs — ENTERED_DR/CR in the journal currency, ACCOUNTED_DR/CR in ledger currency; pick one pair consistently and treat NULLs as zero
The key is JE_HEADER_ID + JE_LINE_NUM, and LEDGER_ID repeats on the lines (documented FK) — a convenient stripe for ledger-scoped extracts. GL_SL_LINK_ID + GL_SL_LINK_TABLE drill back to subledger accounting. Journals arriving from subledgers are summarized per the source's transfer options — line grain is not necessarily document grain.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Header & line
GL_JE_LINES lines join back to their header GL_JE_HEADERS — and the org column — so a line never fans out.
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.FinExtractAM.GlBiccExtractAM.JournalLineExtractPVOOTBI: General Ledger - Journals Real Time
Journal Line data store — composite key JeHeaderId + JeLineNum, mirroring the table's composite PK.
Oracle data-store documentation (opens in new tab)
Fields
16 fields · 2 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | JE_HEADER_ID | The journal — half of the composite key | NUMBER | Key |
| 2 | JE_LINE_NUM | Line number — the other half of the composite key | NUMBER | Key |
| 3 | LEDGER_ID | The ledger, repeated on the lines — a convenient stripe for ledger-scoped extracts | NUMBER | |
| 4 | CODE_COMBINATION_ID | The account combination the line posts to | NUMBER | |
| 5 | PERIOD_NAME | Accounting period | VARCHAR2 | |
| 6 | EFFECTIVE_DATE | Line effective date | DATE | Filter date |
| 7 | STATUS | U unposted, P posted | VARCHAR2 | |
| 8 | ENTERED_DR | Debit in the journal's entered currency — NULL means zero | NUMBER | |
| 9 | ENTERED_CR | Credit in entered currency | NUMBER | |
| 10 | ACCOUNTED_DR | Debit in ledger currency — the pair balance reporting should sum | NUMBER | |
| 11 | ACCOUNTED_CR | Credit in ledger currency | NUMBER | |
| 12 | CURRENCY_CODE | Entered currency of the line | VARCHAR2 | |
| 13 | DESCRIPTION | Line description | VARCHAR2 | |
| 14 | GL_SL_LINK_ID | Drill-back link to subledger accounting | NUMBER | |
| 15 | GL_SL_LINK_TABLE | Which subledger link table the drill-back goes through | VARCHAR2 | |
| 16 | STAT_AMOUNT | Statistical amount on the line | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of GL_JE_LINES on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
8 parameters not filled: <catalog>, <schema>, <LEDGER_ID>, <JE_HEADER_ID>, <JE_LINE_NUM>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : GL_JE_LINES — General ledger journal lines — the debit/credit grain: one row per line with the account combination, entered and accounted amounts, effective date, and the drill-back link to subledger accounting
-- Purpose: Column-selected read of GL_JE_LINES — auto-generated from field metadata
-- Grain : One row per JE_HEADER_ID + JE_LINE_NUM
-- Caution: Amounts come in pairs — ENTERED_DR/CR in the journal currency, ACCOUNTED_DR/CR in ledger currency; pick one pair consistently and treat NULLs as zero
-- Notes : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.JE_HEADER_ID AS "The journal — half of the composite key",
t.JE_LINE_NUM AS "Line number — the other half of the composite key",
t.LEDGER_ID AS "The ledger, repeated on the lines — a convenient stripe for ledger-scoped extracts",
t.CODE_COMBINATION_ID AS "The account combination the line posts to",
t.PERIOD_NAME AS "Accounting period",
t.EFFECTIVE_DATE AS "Line effective date",
t.STATUS AS "U unposted, P posted",
t.ENTERED_DR AS "Debit in the journal's entered currency — NULL means zero",
t.ENTERED_CR AS "Credit in entered currency",
t.ACCOUNTED_DR AS "Debit in ledger currency — the pair balance reporting should sum",
t.ACCOUNTED_CR AS "Credit in ledger currency",
t.CURRENCY_CODE AS "Entered currency of the line",
t.DESCRIPTION AS "Line description",
t.GL_SL_LINK_ID AS "Drill-back link to subledger accounting",
t.GL_SL_LINK_TABLE AS "Which subledger link table the drill-back goes through",
t.STAT_AMOUNT AS "Statistical amount on the line"
FROM <catalog>.<schema>.GL_JE_LINES t
WHERE
t.LEDGER_ID = <LEDGER_ID> -- ledger — the GL stripe; no ORG_ID exists in the GL layer; one ledger or currencies mix
-- AND t.JE_HEADER_ID = <JE_HEADER_ID>
-- AND t.JE_LINE_NUM = <JE_LINE_NUM>
-- AND t.EFFECTIVE_DATE >= DATE '<DATE_FROM>'
-- AND t.EFFECTIVE_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.JE_HEADER_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON GL_JE_HEADERS.JE_HEADER_ID = GL_JE_LINES.JE_HEADER_IDON GL_JE_LINES.LEDGER_ID = GL_LEDGERS.LEDGER_IDON GL_JE_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
More Financials tables
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacks
- AP_INVOICE_DISTRIBUTIONS_ALLPayables invoice distributions — the accounting grain under each line: one row per charged GL account with the amount, accounting date, period, and posted state; where AP spend meets the ledger
- AP_INVOICE_LINES_ALLPayables invoice lines — the goods/services, freight, tax, and prepayment rows under each invoice, carrying the amount, quantity, and the PO/receipt match pointers
- AP_INVOICES_ALLPayables invoice headers — one row per supplier invoice, prepayment, or credit/debit memo, with the supplier, invoice number, amounts, payment status, and approval state; business-unit striped
- AR_CASH_RECEIPTS_ALLCash receipts — one row per receipt entered, with receipt number, date, amount, status, and the paying customer account; the cash side that payment schedules apply against