Search Results xla_amb_components_h




Overview
Explore in AI Chat

Overview

The XLA_AMB_COMPONENTS_H table is owned by the XLA schema within Oracle E-Business Suite Subledger Accounting. It stores the history of non-application specific journal entry setups — specifically analytical criteria and mapping sets — that drive how subledger transactions are transformed into journal entries. The _H suffix indicates historical retention: rows are preserved and versioned rather than overwritten, with the history being refreshed each time the associated components are exported between environments or releases. This makes the table the audit and transport backbone for AMB (Application Mapping Builder) metadata in both 12.1.1 and 12.2.2.

The documented relationship metadata classifies this object as standalone, mined heuristically from its foreign key structure. Under a Data Vault modeling interpretation, this suggests treating it as a hub-like entity anchored on its composite business key (component type, owner, code, version), rather than a link or satellite. The classification is a modeling suggestion, not a declared constraint, so referential dependencies should be confirmed against the actual AMB configuration tables.

Key Information Stored

The table contains 17 documented columns. The most significant are:

The surrogate primary key is XLA_AMB_COMPONENTS_H_PK, while XLA_AMB_COMPONENTS_H_U1 (COMPONENT_TYPE_CODE, COMPONENT_OWNER_CODE, COMPONENT_CODE, APPLICATION_ID, VERSION_NUM) is the documented business-key candidate.

Common Use Cases and Queries

Typical uses include auditing which version of an analytical criterion or mapping set was active during a period, comparing setups across environments after an export, and diagnosing why a transaction generated an unexpected accounting entry. A common filter pattern keys on the component discriminator:

SELECT component_type_code, component_owner_code, component_code, version_num
FROM xla.xla_amb_components_h
WHERE component_type_code = :p_type
AND application_id = :p_app
ORDER BY version_num DESC;

To trace lineage, query where BASE_VERSION_NUM links successive versions. To find the latest exported state, order by VERSION_NUM descending and filter on REQUEST_ID or PROGRAM_UPDATE_DATE. Reporting extracts commonly join to AMB component name or usage views to resolve COMPONENT_CODE into a user-facing label.

Related Objects