Search Results gl_je_headers




Overview
Explore in AI Chat

Overview

GL_JE_HEADERS is the core journal entry header table in the Oracle E-Business Suite General Ledger (GL) module, owned by the GL schema. It stores one row for every journal entry created, imported, or generated in the application, defining the summarizing attributes of a transaction before its individual accounting distributions are recorded in GL_JE_LINES. The table is central to the entire GL posting lifecycle: drafts entered through the Enter Journals form, entries imported from subledgers via the GL_INTERFACE, recurring journal reversals, encumbrance entries, and SLA-generated journals all ultimately persist a header row here. Within the documented 12.2.2 physical schema, GL_JE_HEADERS contains 89 columns, and its Data Vault classification heuristic identifies it as a hub — meaning it functions as the canonical business entity from which many dependent relationships radiate. In practice, GL_JE_HEADERS anchors a star of downstream references, and any query reconciling subledger activity, period close balances, or audit trails typically begins here.

Key Information Stored

The surrogate primary key is JE_HEADER_ID, defined by the constraint GL_JE_HEADERS_PK. Two unique indexes act as business-key candidates: GL_JE_HEADERS_U1 on JE_HEADER_ID and GL_JE_HEADERS_U2 on NAME and JE_BATCH_ID, the latter enforcing that a journal name must be unique within its batch. Among the most operationally significant columns are LEDGER_ID, which ties the entry to a specific ledger; JE_BATCH_ID, linking the header to its batch in GL_JE_BATCHES; JE_CATEGORY and JE_SOURCE, which classify the entry (for example, Payables or Manual); PERIOD_NAME and STATUS, which determine accounting period and posting state; CURRENCY_CODE and ACTUAL_FLAG, which identify currency and whether the entry is actual, budget, or encumbrance; and the control totals CONTROL_TOTAL, RUNNING_TOTAL_DR, RUNNING_TOTAL_CR, RUNNING_TOTAL_ACCOUNTED_DR, and RUNNING_TOTAL_ACCOUNTED_CR. Reversal tracking is handled through REVERSED_JE_HEADER_ID, ACCRUAL_REV_JE_HEADER_ID, and ACCRUAL_REV_STATUS, while BALANCED_JE_FLAG, DATE_CREATED, and POSTED_DATE capture balance status, creation, and posting timestamps. Document sequencing fields such as DOC_SEQUENCE_ID and DOC_SEQUENCE_VALUE support statutory numbering.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing a subledger journal back to its GL entry, identifying unposted or unbalanced journals before period close, and reconciling control totals against the sum of detail lines. A representative query returns journal metadata for a given period and ledger:

  • SELECT h.je_header_id, h.name, h.period_name, h.status, h.currency_code FROM gl_je_headers h WHERE h.ledger_id = :ledger_id AND h.period_name = :period_name;
  • Joining to batches: SELECT b.name batch, h.name, h.status FROM gl_je_headers h, gl_je_batches b WHERE h.je_batch_id = b.je_batch_id AND h.status = 'U';
  • Balance validation: comparing h.control_total with SUM(lines.accounted_dr) - SUM(lines.accounted_cr) from GL_JE_LINES.
  • Reversal identification: SELECT je_header_id, name FROM gl_je_headers WHERE reversed_je_header_id IS NOT NULL;

These patterns underpin period-close dashboards, journal audit reports, and interface-to-GL reconciliation utilities.

Related Objects

GL_JE_HEADERS is heavily referenced across modules. Its most significant relationships are documented through foreign keys and dependent tables:

Together these objects form the journal entry graph that the GL period-close and reconciliation processes depend upon.