Search Results ap_check_transmissions




Overview

The GL_JE_HEADERS table is a core data structure within the Oracle E-Business Suite General Ledger (GL) module, specifically for releases 12.1.1 and 12.2.2. It serves as the header-level repository for all journal entries, which are the fundamental records for posting financial transactions to the general ledger. Each row in this table represents a distinct journal entry, containing the overarching control and descriptive information that applies to all lines within that entry. The table's integrity is central to the GL's accounting engine, as it maintains critical relationships to journal batches, ledgers, currencies, and other journal entries for processes like reversals and recurring journals.

Key Information Stored

The table's primary key is the system-generated identifier JE_HEADER_ID. A unique key also exists on the combination of JE_BATCH_ID and NAME, enforcing uniqueness of journal names within a batch. Key columns include LEDGER_ID, which ties the journal to a specific accounting ledger, and CURRENCY_CODE, defining the journal's transaction currency. Status and control are managed through columns such as STATUS (e.g., 'U' for Unposted, 'P' for Posted), PERIOD_NAME, and EFFECTIVE_DATE. The table also captures inter-journal relationships via columns like REVERSED_JE_HEADER_ID, PARENT_JE_HEADER_ID, ACCRUAL_REV_JE_HEADER_ID, and FROM_RECURRING_HEADER_ID, which are essential for tracking reversal chains, summary journals, and template-based entries.

Common Use Cases and Queries

This table is central to journal inquiry, audit reporting, and reconciliation. A common query retrieves unposted journals for a specific ledger and period to review before posting:

  • SELECT je_header_id, name, period_name, effective_date FROM gl_je_headers WHERE ledger_id = 1001 AND status = 'U' AND period_name = 'JAN-2024';

Another frequent use case is tracing the reversal of a specific journal entry:

  • SELECT reversed_je_header_id FROM gl_je_headers WHERE je_header_id = <original_journal_id>;

For consolidated reporting, analysts often join GL_JE_HEADERS with GL_JE_LINES and GL_CODE_COMBINATIONS to analyze transaction volume and balances by account segment.

Related Objects

GL_JE_HEADERS has extensive integration across EBS. Its primary child table is GL_JE_LINES, which stores the detailed accounting line items. It is contained within a GL_JE_BATCHES parent record. As per the metadata, it is referenced by numerous subledger and financial tables, including AP_CHECK_TRANSMISSIONS, AP_INVOICE_TRANSMISSIONS, CE_STATEMENT_RECONCILS_ALL, and various Fixed Assets depreciation tables (FA_DEPRN_DETAIL, FA_MC_DEPRN_DETAIL). Key foreign key relationships exist with GL_LEDGERS, GL_JE_BATCHES, FND_CURRENCIES, GL_DAILY_CONVERSION_TYPES, GL_BUDGET_VERSIONS, and GL_ENCUMBRANCE_TYPES, highlighting its role in currency, budgeting, and encumbrance accounting.