Search Results xla_ae_headers_gt_n1

Overview

XLA.XLA_AE_HEADERS_GT is a global temporary table in the Subledger Accounting (XLA) schema of Oracle E-Business Suite. It serves as the staging structure for accounting event headers produced by the Subledger Accounting Engine during the create-accounting, transfer-to-GL, and reporting workflows. Header-level rows represent a single accounting entry for a combination of a subledger event, ledger, and balance type, and are the parent of the corresponding accounting entry lines staged in the companion lines table.

The table is defined with a data duration of SYS$TRANSACTION, meaning rows are visible only to the session that inserted them and are cleared at transaction commit. This makes XLA_AE_HEADERS_GT effectively a private, session-scoped workspace rather than a persistent repository. Under the supplied metadata's heuristic Data Vault classification, the object is modeled as standalone; from a modeling perspective it may be treated as a transient staging construct rather than a durable hub, link, or satellite, since its lifecycle is confined to a single concurrent program run. The physical definition comprises 135 columns, a PCTFREE of 10 and PCTUSED of 40, with one unique index and one non-unique index.

Key Information Stored

The table's business identity is anchored by the unique index XLA_AE_HEADERS_GT_U1, whose columns are AE_HEADER_ID, LEDGER_ID, BALANCE_TYPE_CODE and HEADER_NUM. AE_HEADER_ID is the surrogate key for the header; LEDGER_ID scopes the entry to a specific ledger; BALANCE_TYPE_CODE distinguishes actual from budget or encumbrance balances; and HEADER_NUM is the externally meaningful accounting entry number assigned within that ledger and balance type. Together these four columns form the candidate business key and enforce uniqueness within the session.

Other significant columns include ENTITY_ID and EVENT_ID, which identify the source transaction entity and the accounting event from which the entry was generated; EVENT_TYPE_CODE and EVENT_NUMBER, which classify the event; ACCOUNTING_DATE and PERIOD_NAME, which drive the GL period into which the entry will post; JE_CATEGORY_NAME, which determines the journal category; and ACCOUNTING_ENTRY_STATUS_CODE and GL_TRANSFER_STATUS_CODE, which convey processing state through to General Ledger. BALANCE_TYPE_CODE, BUDGET_VERSION_ID and ENCUMBRANCE_TYPE_ID further qualify the balance context. PARENT_HEADER_ID supports the hierarchical relationship between headers, and is indexed by the non-unique index XLA_AE_HEADERS_GT_N1. A large block of ANC_ID_1 through ANC_ID_100 columns provides the descriptive flexfield-style attribute segment values that carry source-specific context into the accounting entry.

Common Use Cases and Queries

Because the table is temporary, its principal diagnostic value is during the execution of the Subledger Accounting programs, where a session can inspect the headers it has staged before commit. Typical scenarios include validating that an event produced the expected number of accounting entries, reconciling HEADER_NUM assignment against GL transfer, and tracing the parent-child relationship between reversals and original entries.

• Session-scoped inspection of staged headers, for example selecting AE_HEADER_ID, LEDGER_ID, BALANCE_TYPE_CODE, HEADER_NUM, ACCOUNTING_DATE and JE_CATEGORY_NAME from XLA.XLA_AE_HEADERS_GT.
• Filtering by event to review the accounting produced for a single subledger event using ENTITY_ID and EVENT_ID.
• Auditing parent-child header hierarchies by joining the table to itself on PARENT_HEADER_ID = AE_HEADER_ID, exploiting index XLA_AE_HEADERS_GT_N1.
• Verifying GL transfer readiness by reviewing rows where GL_TRANSFER_STATUS_CODE or ACCOUNTING_ENTRY_STATUS_CODE indicates incomplete processing.
• Confirming business-key uniqueness against index XLA_AE_HEADERS_GT_U1 across AE_HEADER_ID, LEDGER_ID, BALANCE_TYPE_CODE and HEADER_NUM.

Because rows are deleted at transaction end, these queries are meaningful only within the inserting session; for persistent analysis, equivalent data should be accessed from the permanent SLA tables after the accounting is finalized.

Related Objects

The table participates in two documented foreign key relationships and is tightly coupled to the wider Subledger Accounting and General Ledger schemas.

• XLA_AE_HEADERS — the permanent accounting entry headers table, the persistent counterpart to this temporary structure.
• XLA_AE_LINES_GT — the temporary lines table, joined to headers on AE_HEADER_ID.
• GL_ENCUMBRANCE_TYPES — referenced through the ENCUMBRANCE_TYPE_ID foreign key, qualifying encumbrance balances.
• FND_DOCUMENT_SEQUENCES — referenced through the DOC_SEQUENCE_ID foreign key, supplying document sequence numbering for the entry.
• XLA_EVENTS — the accounting event that drives header generation, linked through EVENT_ID and ENTITY_ID.
• GL_JE_HEADERS — the General Ledger journal header ultimately created when headers are transferred, aligned by ledger and entry number.