GL_JE_HEADERS
Product: GLtransactionGeneral ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totals
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.
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.JournalHeaderExtractPVOOTBI: 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
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | JE_HEADER_ID | Surrogate key of the journal | NUMBER | Key |
| 2 | LEDGER_ID | The ledger — GL's stripe; there is no ORG_ID in the GL layer | NUMBER | |
| 3 | JE_BATCH_ID | The journal batch (batch table not cataloged) | NUMBER | |
| 4 | NAME | Journal name | VARCHAR2 | |
| 5 | PERIOD_NAME | Accounting period | VARCHAR2 | |
| 6 | JE_CATEGORY | Journal category — what kind of transaction the journal represents | VARCHAR2 | |
| 7 | JE_SOURCE | Journal source — where the journal came from (Payables, Receivables, Manual…) | VARCHAR2 | |
| 8 | STATUS | U unposted, P posted — plus documented error codes; no named lookup type | VARCHAR2 | |
| 9 | ACTUAL_FLAG | Balance type — actual, budget, or encumbrance; filter it or totals mix | VARCHAR2 | |
| 10 | CURRENCY_CODE | Journal currency | VARCHAR2 | |
| 11 | DEFAULT_EFFECTIVE_DATE | Default effective date for the journal's lines | DATE | Filter date |
| 12 | POSTED_DATE | When the journal posted | DATE | |
| 13 | RUNNING_TOTAL_ACCOUNTED_DR | Journal debit total in ledger currency | NUMBER | |
| 14 | RUNNING_TOTAL_ACCOUNTED_CR | Journal credit total in ledger currency | NUMBER | |
| 15 | REVERSED_JE_HEADER_ID | The journal this one reverses (self-referencing) | NUMBER | |
| 16 | JE_FROM_SLA_FLAG | Whether the journal arrived from subledger accounting | VARCHAR2 |
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.
-- ============================================================
-- 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
ON GL_JE_HEADERS.JE_HEADER_ID = GL_JE_LINES.JE_HEADER_IDON 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