Search Results xla_ae_header_acs_n1

Overview

The table XLA.XLA_AE_HEADER_ACS is a subledger accounting repository within the Oracle E-Business Suite (EBS) database, owned by the XLA schema. Its documented role is to store the relationship between subledger journal entry lines and supporting reference detail values. In practical terms, each row associates a subledger journal entry header — identified by AE_HEADER_ID — with one or more analytical criterion values (supporting references) that describe the accounting context under which the entry was generated.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its transactional nature. Its documented heuristic Data Vault classification is standalone, meaning the metadata mining did not surface foreign-key dependencies tying it into a hub/link/satellite network. As a modeling suggestion, this object behaves like a satellite-style attribute table keyed by a composite business key, with the supported accounting header acting as its logical parent.

Key Information Stored

The table exposes ten documented columns. The most significant grouping is the composite key that drives uniqueness and access:

• AE_HEADER_ID (NUMBER 15) — the journal entry identifier; the linkage back to the subledger accounting header.
• ANALYTICAL_CRITERION_CODE (VARCHAR2 30) — the supporting reference code.
• ANALYTICAL_CRITERION_TYPE_CODE (VARCHAR2 30) — the supporting reference type code that qualifies the criterion.
• AMB_CONTEXT_CODE (VARCHAR2 30) — the AMB (Application Message Board) context code, defining the transactional context in which the criterion applies.
• OBJECT_VERSION_NUMBER (NUMBER 15) — the optimistic locking / versioning column maintained by the XLA framework.
• AC1, AC2, AC3, AC4, AC5 (VARCHAR2 30 each) — five supporting reference detail value columns that capture the actual analytical criterion values associated with the header.

The documented primary key is XLA_AE_HEADER_ACS_PK over (AE_HEADER_ID, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, AMB_CONTEXT_CODE). The unique index XLA_AE_HEADER_ACS_U1 enforces the same four-column business key on APPS_TS_TX_IDX, confirming that this four-column combination — not the surrogate-like header ID alone — is the true business key. The non-unique index XLA_AE_HEADER_ACS_N1 covers the three criterion columns (code, type, context) to support criterion-centric lookups.

Common Use Cases and Queries

The principal use case is supporting reference analysis: reconciling subledger journal entries to the analytical criteria that selected them. Practitioners query this table to trace why a given journal entry was created, to report on supporting reference distributions, or to validate that all entries carry the expected criterion values.

A typical retrieval by header:

• SELECT AE_HEADER_ID, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, AMB_CONTEXT_CODE, AC1, AC2, AC3, AC4, AC5 FROM XLA.XLA_AE_HEADER_ACS WHERE AE_HEADER_ID = :p_header_id;

A criterion-driven report, leveraging the N1 index:

• SELECT ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, COUNT(*) FROM XLA.XLA_AE_HEADER_ACS WHERE AMB_CONTEXT_CODE = :p_context GROUP BY ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE;

Because the transaction data is date-stamped on the journal header rather than here, date-range reporting should join to the header by AE_HEADER_ID rather than filter on this table directly.

Related Objects

The metadata records XLA_AE_HEADER_ACS as a standalone object that references no database objects directly, but it is referenced by the APPS.XLA_AE_HEADER_ACS synonym. Logical relationships — inferred from the AE_HEADER_ID column — connect it to the surrounding XLA journal model:

• XLA_AE_HEADERS — the subledger journal entry header; join on AE_HEADER_ID.
• XLA_AE_LINES — journal entry lines that consume the supporting reference values; linked via the header's AE_HEADER_ID.
• XLA_AE_HEADER_ACS (APPS synonym) — the application-facing access path used by Subledger Accounting reports and concurrent programs.
• XLA_SUPPORTING_REFERENCES / XLA_ANALYTICAL_CRITERIA — the definition sources for the criterion code, type, and context values stored here.

Collectively these objects form the traceability chain from a posted accounting entry back to the supporting reference criteria that generated it.