Results for “xla_ae_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The XLA_AE_HEADERS table is the central repository for subledger journal entry headers within Oracle Subledger Accounting (XLA). Owned by the XLA schema, it stores the accounting representation of every subledger transaction that has been accounted, whether generated by Payables, Receivables, Assets, Inventory, or any other source application subscribing to the Subledger Accounting engine. Each row corresponds to a single subledger journal entry, and the table maintains a one-to-many relationship with accounting events: one accounting event can produce multiple journal entry headers, reflecting situations such as multi-ledger accounting, secondary ledger postings, or repeated accounting runs.

From a Data Vault modeling perspective, the metadata classifies this table heuristically as standalone. In practice this suggests it behaves most like a satellite anchored to an accounting event hub — the row is descriptive state about the accounting of an event rather than a pure junction link. Modelers building a warehouse should treat EVENT_ID as the natural hub reference and persist the header attributes as satellite history.

Key Information Stored

At the core of the table sits the surrogate primary key AE_HEADER_ID, enforced by XLA_AE_HEADERS_PK. A unique index, XLA_AE_HEADERS_U1, spans AE_HEADER_ID and APPLICATION_ID, effectively the business-key candidate for cross-application uniqueness.

• APPLICATION_ID, LEDGER_ID — identify the owning application and the ledger for which the entry was created.
• ENTITY_ID, EVENT_ID, EVENT_TYPE_CODE — tie the header back to the accounting event source.
• ACCOUNTING_DATE, PERIOD_NAME, REFERENCE_DATE, COMPLETED_DATE — the principal date and period attributes governing GL transfer timing.
• JE_CATEGORY_NAME, ACCOUNTING_ENTRY_STATUS_CODE, ACCOUNTING_ENTRY_TYPE_CODE — classification and lifecycle state of the entry.
• GL_TRANSFER_STATUS_CODE, GL_TRANSFER_DATE — indicate whether the entry has been posted to General Ledger.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE, DOC_SEQUENCE_ASSIGN_ID — document sequencing metadata for legal numbering.
• ZERO_AMOUNT_FLAG, ACCRUAL_REVERSAL_FLAG, NEED_BAL_FLAG — processing control flags.
• PARENT_AE_HEADER_ID, PARENT_AE_LINE_NUM — support parent/child entry hierarchies.

Common Use Cases and Queries

The most frequent query pattern retrieves all headers for a given accounting event or ledger and period, joined to lines for balancing. Analysts also audit GL transfer status to reconcile entries not yet posted.

SELECT ae_header_id, je_category_name, accounting_entry_status_code,
       gl_transfer_status_code, accounting_date
FROM   xla_ae_headers
WHERE  event_id = :event_id;

Reconciliation reports typically aggregate by ledger and period to verify that all accounting entries transferred successfully, while document sequencing audits isolate headers with null sequence values.

Related Objects

• XLA_AE_LINES — child table joined on AE_HEADER_ID, carrying the debit and credit distributions.
• FND_DOCUMENT_SEQUENCES — referenced through DOC_SEQUENCE_ID.
• GL_ENCUMBRANCE_TYPES — referenced through ENCUMBRANCE_TYPE_ID.
• XLA_UPG_BATCHES — referenced through UPG_BATCH_ID for upgrade tracking.
• XLA_EVENTS — source accounting events joined on EVENT_ID.
• GL_JE_HEADERS — destination after successful GL transfer.