Search Results xla_ae_header_acs




Overview
Explore in AI Chat

Overview

XLA_AE_HEADER_ACS is a Subledger Accounting (XLA) table in the Oracle E-Business Suite database, owned by the XLA schema. It stores the relationship between subledger journal entry headers and analytic criteria or supporting reference detail values, enabling Subledger Accounting to attribute journal entries to user-defined analytical dimensions such as product line, cost center, or project. The table functions as the header-level anchor for analytical criteria captured on subledger journal entries and is populated during the Create Accounting process.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone structure. It does not participate in the FK-defined parent/child relationships typical of hubs or links, so it is best treated as an independent reference or satellite-style container keyed by its own composite business key. The unique index XLA_AE_HEADER_ACS_U1 confirms the natural key on (AE_HEADER_ID, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, AMB_CONTEXT_CODE), and the primary key constraint XLA_AE_HEADER_ACS_PK enforces the same combination.

Key Information Stored

The documented schema contains 10 columns. The most significant are:

  • AE_HEADER_ID — Foreign reference to the accounting entry header in XLA_AE_HEADERS. Combined with the analytical criterion columns, it forms the leading edge of the primary key XLA_AE_HEADER_ACS_PK and the unique index XLA_AE_HEADER_ACS_U1.
  • ANALYTICAL_CRITERION_CODE — Business identifier of the analytical criterion (for example, a product or segment code) assigned to the journal entry.
  • ANALYTICAL_CRITERION_TYPE_CODE — Classifies the analytical criterion, distinguishing user-defined criteria categories.
  • AMB_CONTEXT_CODE — Context code from the Application Message Board, denoting the context in which the analytical criterion is registered.
  • AC1 through AC5 — Five attribute columns holding the actual supporting reference detail values associated with the analytical criterion. These carry the descriptive values used in reporting and reconciliation.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OA Framework for concurrent update control.

The surrogate identity is effectively the composite primary key; no separate sequence-based surrogate is documented. Business-key candidates are the composite captured in XLA_AE_HEADER_ACS_U1.

Common Use Cases and Queries

Typical uses include reconciling subledger journal entries to management dimensions, building analytical reports on accounting distributions, and auditing how supporting references were attributed during Create Accounting. A representative join pattern:

  • Join to XLA_AE_HEADERS on AE_HEADER_ID = AE_HEADER_ID to retrieve accounting entry metadata such as accounting date and ledger.
  • Join to XLA_AE_LINES for line-level supporting reference information, which links to the header through AE_HEADER_ID.
  • Filter by ANALYTICAL_CRITERION_TYPE_CODE to isolate a specific criterion class.
  • Aggregate AC1 through AC5 to summarize balances by analytical dimension.

Because the table is populated during accounting creation, post-close reporting should read it in read-only mode. Users investigating missing supporting references should compare header counts in XLA_AE_HEADERS against rows in XLA_AE_HEADER_ACS.

Related Objects

  • XLA_AE_HEADERS — Parent accounting entry header; joined on AE_HEADER_ID.
  • XLA_AE_LINES — Line-level journal details sharing AE_HEADER_ID.
  • XLA_AE_HEADER_ACS reference indexes such as XLA_AE_HEADER_ACS_PK and XLA_AE_HEADER_ACS_U1 govern uniqueness.
  • XLA_ANALYTICAL_CRITERIA (or equivalent XLA criteria definition tables) — Defines ANALYTICAL_CRITERION_CODE values.
  • XLA_ACCOUNTING_ERRORS — Diagnostics for entries that fail accounting and therefore lack header ACS rows.