Skip to content
Fusion Reference

GL_JE_LINES

Product: GLtransaction

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

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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.JournalLineExtractPVO
    OTBI: General Ledger - Journals Real Time

    Journal Line data store — composite key JeHeaderId + JeLineNum, mirroring the table's composite PK.

    Oracle data-store documentation →

Fields

16 fields · 2 key

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_LINESon 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
-- ============================================================
-- 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
  1 = 1  -- no partition column on this table; the filters below are optional
  -- 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;

7 parameters not filled: <catalog>, <schema>, <JE_HEADER_ID>, <JE_LINE_NUM>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

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 Financialstables →

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.