Search Results xla_ae_headers

Overview

The XLA_AE_HEADERS table is a core data repository within the Subledger Accounting (XLA) module of Oracle E-Business Suite (EBS) Releases 12.1.1 and 12.2.2. It serves as the primary storage location for subledger journal entry headers. These headers represent the accounting outcome generated from business transactions processed through subledgers, such as Payables (AP), Receivables (AR), and Assets (FA). The table embodies a fundamental architectural principle of Subledger Accounting: the one-to-many relationship between an accounting event and its resulting journal entries. A single accounting event can produce multiple journal entries, each with a distinct header record in this table, enabling detailed audit trails and supporting multiple representations of accounting data.

Key Information Stored

Each row in XLA_AE_HEADERS defines a unique subledger journal entry. The table's primary key is the AE_HEADER_ID, a system-generated unique identifier. While the full column list is extensive, critical fields typically include APPLICATION_ID (identifying the source subledger), LEDGER_ID (the accounting setup), EVENT_ID (linking back to the source accounting event in XLA_EVENTS), and ENTITY_ID (identifying the business transaction entity). Other essential columns store the accounting date, journal entry description, creation details, and status flags that indicate the journal entry's posting readiness and its relationship with the General Ledger (GL).

Common Use Cases and Queries

This table is central to troubleshooting, reconciliation, and custom reporting for subledger accounting. Common use cases include tracing the accounting impact of a specific transaction from a subledger to its journal entries, identifying unposted subledger entries, and reconciling subledger journals to the General Ledger's GL_JE_HEADERS table. A fundamental query pattern joins XLA_AE_HEADERS to XLA_AE_LINES to retrieve complete journal entries.

• Sample Query: To find journal headers for a specific Payables invoice:
  SELECT xah.ae_header_id, xah.accounting_date, xah.description
FROM xla_ae_headers xah
WHERE xah.application_id = 200
AND xah.entity_id = (SELECT entity_id FROM xla_transaction_entities WHERE source_id_int_1 = <invoice_id>);
• Reconciliation: Joining XLA_AE_HEADERS to GL_JE_HEADERS on the reference columns (JE_HEADER_ID, JE_SOURCE, JE_CATEGORY) is standard for reconciling subledger and general ledger.

Related Objects

XLA_AE_HEADERS is the parent table in a tightly integrated hierarchy. Its most direct child is XLA_AE_LINES, which stores the individual accounting lines for each journal entry header. It is sourced from XLA_EVENTS, which provides the accounting event that triggered the journal creation. For reconciliation and posting, it relates to GL_JE_HEADERS in the General Ledger. Key supporting objects include XLA_TRANSACTION_ENTITIES (for the business transaction context) and the public view XLA_AE_HEADERS_V, which is often preferred for reporting due to its built-in security. The table is primarily accessed via the Subledger Accounting (SLA) APIs rather than through direct DML.