Skip to content
Fusion Reference

GL_JE_HEADERS

Product: GLtransaction

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

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

Fields

16 fields · 1 key

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

6 parameters not filled: <catalog>, <schema>, <JE_HEADER_ID>, <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_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 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.