Skip to content
Fusion Reference

GL_JE_HEADERS

Product: GLtransactionLedger-striped (LEDGER_ID)

General ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totals

Identity
Module: FinancialsLedger-striped (LEDGER_ID)
EBS equivalents (2)
Notes

Ledger-striped (LEDGER_ID), not BU-striped — there is no ORG_ID anywhere in the GL layer. STATUS is page-enumerated (U unposted, P posted, plus error codes) but carries no named lookup type — no ladder ships. ACTUAL_FLAG separates actual, budget, and encumbrance balances — filter it or totals mix. The batch level (GL_JE_BATCHES) is documented but not cataloged.

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_HEADERS is the header for its lines in GL_JE_LINES.

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

    Journals (header) data store — keyed on JeHeaderId (the GL stores print short attribute names, without table prefixes).

    Oracle data-store documentation (opens in new tab)

Fields

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1JE_HEADER_IDSurrogate key of the journalNUMBER
Key
2LEDGER_IDThe ledger — GL's stripe; there is no ORG_ID in the GL layerNUMBER
3JE_BATCH_IDThe journal batch (batch table not cataloged)NUMBER
4NAMEJournal nameVARCHAR2
5PERIOD_NAMEAccounting periodVARCHAR2
6JE_CATEGORYJournal category — what kind of transaction the journal representsVARCHAR2
7JE_SOURCEJournal source — where the journal came from (Payables, Receivables, Manual…)VARCHAR2
8STATUSU unposted, P posted — plus documented error codes; no named lookup typeVARCHAR2
9ACTUAL_FLAGBalance type — actual, budget, or encumbrance; filter it or totals mixVARCHAR2
10CURRENCY_CODEJournal currencyVARCHAR2
11DEFAULT_EFFECTIVE_DATEDefault effective date for the journal's linesDATE
Filter date
12POSTED_DATEWhen the journal postedDATE
13RUNNING_TOTAL_ACCOUNTED_DRJournal debit total in ledger currencyNUMBER
14RUNNING_TOTAL_ACCOUNTED_CRJournal credit total in ledger currencyNUMBER
15REVERSED_JE_HEADER_IDThe journal this one reverses (self-referencing)NUMBER
16JE_FROM_SLA_FLAGWhether the journal arrived from subledger accountingVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of GL_JE_HEADERS 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

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

-- ============================================================
-- Table  : GL_JE_HEADERS — General ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totals
-- Purpose: Column-selected read of GL_JE_HEADERS — auto-generated from field metadata
-- Grain  : One row per JE_HEADER_ID
-- 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 "Surrogate key of the journal",
  t.LEDGER_ID AS "The ledger — GL's stripe; there is no ORG_ID in the GL layer",
  t.JE_BATCH_ID AS "The journal batch (batch table not cataloged)",
  t.NAME AS "Journal name",
  t.PERIOD_NAME AS "Accounting period",
  t.JE_CATEGORY AS "Journal category — what kind of transaction the journal represents",
  t.JE_SOURCE AS "Journal source — where the journal came from (Payables, Receivables, Manual…)",
  t.STATUS AS "U unposted, P posted — plus documented error codes; no named lookup type",
  t.ACTUAL_FLAG AS "Balance type — actual, budget, or encumbrance; filter it or totals mix",
  t.CURRENCY_CODE AS "Journal currency",
  t.DEFAULT_EFFECTIVE_DATE AS "Default effective date for the journal's lines",
  t.POSTED_DATE AS "When the journal posted",
  t.RUNNING_TOTAL_ACCOUNTED_DR AS "Journal debit total in ledger currency",
  t.RUNNING_TOTAL_ACCOUNTED_CR AS "Journal credit total in ledger currency",
  t.REVERSED_JE_HEADER_ID AS "The journal this one reverses (self-referencing)",
  t.JE_FROM_SLA_FLAG AS "Whether the journal arrived from subledger accounting"
FROM <catalog>.<schema>.GL_JE_HEADERS 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.DEFAULT_EFFECTIVE_DATE >= DATE '<DATE_FROM>'
  -- AND t.DEFAULT_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.

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_HEADERSGL_LEDGERSforeign key · N:1
    ON GL_JE_HEADERS.LEDGER_ID = GL_LEDGERS.LEDGER_ID
  • GL_JE_HEADERSGL_JE_HEADERSforeign key · N:1
    ON GL_JE_HEADERS1.REVERSED_JE_HEADER_ID = GL_JE_HEADERS2.JE_HEADER_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.