Search Results gl_je_headers_u2

Overview

GL.GL_JE_HEADERS is the core header table of the Oracle General Ledger journal entry model in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a single journal entry, which is the parent of one or more journal lines stored in GL_JE_LINES. There is a one-to-many relationship between journal entry batches (GL_JE_BATCHES) and journal entries, so every row carries a JE_BATCH_ID that links it to its batch. Functionally, the table corresponds to the Journals window of the Enter Journals form, and it is the authoritative source for journal status, posting dates, currency conversion attributes, accrual reversal configuration, and intercompany balancing metadata.

From a Data Vault modeling perspective, the ETRM relationship classification of this object is hub. It is best treated as the business-key hub for the journal entry entity, since it carries the natural business key candidates and is referenced by a large population of dependent tables.

Key Information Stored

The table contains 89 documented columns. The most operationally significant are:

• JE_HEADER_ID — the surrogate primary key (GL_JE_HEADERS_PK).
• NAME and JE_BATCH_ID — together form the unique business key GL_JE_HEADERS_U2. This is the index users search for when querying by journal name within a batch.
• STATUS — journal status: 'U' unposted, 'P' posted; other values indicate error conditions such as invalid period, unbalanced entry, or invalid code combination.
• LEDGER_ID — the ledger the entry posts to.
• JE_SOURCE, JE_CATEGORY, PERIOD_NAME, CURRENCY_CODE, ACTUAL_FLAG — accounting context of the entry.
• DATE_CREATED, POSTED_DATE, UNIQUE_DATE, EARLIEST_POSTABLE_DATE — lifecycle timestamps.
• BALANCED_JE_FLAG, BALANCING_SEGMENT_VALUE, MULTI_BAL_SEG_FLAG, DR_BAL_SEG_VALUE, CR_BAL_SEG_VALUE — balancing and multi-balancing-segment information.
• CONVERSION_FLAG — 'N' indicates a manually changed converted amount that the posting program must not re-convert.
• ACCURAL_REV_* columns and REVERSED_JE_HEADER_ID, PARENT_JE_HEADER_ID — reversal and recurring-entry lineage.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE, LOCAL_DOC_SEQUENCE_* — document sequencing for statutory numbering.

Common Use Cases and Queries

Typical uses include journal posting status reporting, period-close balancing checks, reversal tracking, and reconciliation of subledger transfers. A query to list unposted journals for a ledger and period:

SELECT h.je_header_id, h.name, h.period_name, h.status, h.posted_date
FROM   gl_je_headers h
WHERE  h.ledger_id = :ledger_id
AND    h.period_name = :period_name
AND    h.status = 'U';

To find entries created from a specific source or category, filter on JE_SOURCE and JE_CATEGORY. To trace reversal pairs, join REVERSED_JE_HEADER_ID back to JE_HEADER_ID. To identify entries whose converted amounts were manually overridden, filter CONVERSION_FLAG = 'N', which is only possible when the profile MULTIPLE_RATES_PER_JE is 'Yes'. Joining to GL_JE_LINES on JE_HEADER_ID produces the detail balances used for trial balance extracts.

Related Objects

• GL_JE_BATCHES — parent batch, joined via JE_BATCH_ID.
• GL_JE_LINES — journal lines, joined via JE_HEADER_ID.
• GL_LEDGERS — ledger definition, joined via LEDGER_ID.
• GL_INTERFACE — inbound journal import, references JE_HEADER_ID.
• GL_IMPORT_REFERENCES — links headers to source subledger transactions.
• GL_DAILY_CONVERSION_TYPES and FND_CURRENCIES — currency and rate context.
• FA_DEPRN_DETAIL, AP_INVOICE_TRANSMISSIONS, CE_STATEMENT_RECONCILS_ALL — downstream references from subledgers.
• GL_JE_SEGMENT_VALUES — balancing segment detail, joined via JE_HEADER_ID.