Skip to content
Fusion Reference

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

Identity
Module: FinancialsLedger-striped (LEDGER_ID)Header: GL_JE_HEADERS
EBS equivalents (2)
Grain note

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

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.

Fields

16 fields · 2 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1JE_HEADER_IDThe journal — half of the composite keyNUMBER
Key
2JE_LINE_NUMLine number — the other half of the composite keyNUMBER
Key
3LEDGER_IDThe ledger, repeated on the lines — a convenient stripe for ledger-scoped extractsNUMBER
4CODE_COMBINATION_IDThe account combination the line posts toNUMBER
5PERIOD_NAMEAccounting periodVARCHAR2
6EFFECTIVE_DATELine effective dateDATE
Filter date
7STATUSU unposted, P postedVARCHAR2
8ENTERED_DRDebit in the journal's entered currency — NULL means zeroNUMBER
9ENTERED_CRCredit in entered currencyNUMBER
10ACCOUNTED_DRDebit in ledger currency — the pair balance reporting should sumNUMBER
11ACCOUNTED_CRCredit in ledger currencyNUMBER
12CURRENCY_CODEEntered currency of the lineVARCHAR2
13DESCRIPTIONLine descriptionVARCHAR2
14GL_SL_LINK_IDDrill-back link to subledger accountingNUMBER
15GL_SL_LINK_TABLEWhich subledger link table the drill-back goes throughVARCHAR2
16STAT_AMOUNTStatistical amount on the lineNUMBER

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.

Query parameters

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

  • GL_JE_HEADERSGL_JE_LINESheader line · 1:N
    ON GL_JE_HEADERS.JE_HEADER_ID = GL_JE_LINES.JE_HEADER_ID
  • GL_JE_LINESGL_LEDGERSforeign key · N:1
    ON GL_JE_LINES.LEDGER_ID = GL_LEDGERS.LEDGER_ID
  • GL_JE_LINESGL_CODE_COMBINATIONSforeign key · N:1
    ON GL_JE_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID

Browse more Financials tables

More Financials tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.