Search Results component_owner_code

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:

COMPONENT_TYPE_CODE — the discriminator identifying the kind of setup object, such as analytical criteria versus mapping set.
COMPONENT_OWNER_CODE — the owning product or application context of the component.
COMPONENT_CODE — the internal identifier of the specific setup object being versioned.
VERSION_NUM — the version sequence for the component; together with the preceding three columns it forms the primary key XLA_AMB_COMPONENTS_H_PK.
BASE_VERSION_NUM — the version from which this historical row was derived, enabling lineage traversal.
APPLICATION_ID — the application owning the component; included in the unique index XLA_AMB_COMPONENTS_H_U1.
LEAPFROG_FLAG — indicates whether the component was carried forward through a leapfrog export.
OBJECT_VERSION_NUMBER — optimistic locking column used by the AMB concurrent programs.
CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — the concurrent program and request context that generated the historical row.

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

XLA_AMB_COMPONENTS — the current (non-history) setup table, joined on COMPONENT_TYPE_CODE, COMPONENT_OWNER_CODE, COMPONENT_CODE, APPLICATION_ID, and VERSION_NUM.
XLA_AMB_COMPONENT_DETAILS / component definition tables — resolve the component code into constituent criteria or mapping rules.
XLA_AMB_MAPPING_SETS and XLA_AMB_CRITERIA — the configurable objects whose versions are recorded here.
XLA_ACCOUNTING_PROGRAMS — the concurrent program definitions referenced by PROGRAM_ID and PROGRAM_APPLICATION_ID.
FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for export run context.
FND_APPLICATION_VL — resolves APPLICATION_ID to an application name.
XLA_AMB_PUB / AMB import-export APIs — programmatically populate and consume history rows.

Table: XLA_AMB_COMPONENTS_H 12.2.2
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_AMB_COMPONENTS_H, object_name:XLA_AMB_COMPONENTS_H, status:VALID, product: XLA - Subledger Accounting , description: The XLA_AMB_COMPONENTS_H table stores the history of the non-application specific journal entry setups, i.e. analytical criteria and mapping sets. The history is updated when the components are exported. , implementation_dba_data: XLA.XLA_AMB_COMPONENTS_H ,
Table: XLA_AMB_COMPONENTS_H 12.1.1
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_AMB_COMPONENTS_H, object_name:XLA_AMB_COMPONENTS_H, status:VALID, product: XLA - Subledger Accounting , description: The XLA_AMB_COMPONENTS_H table stores the history of the non-application specific journal entry setups, i.e. analytical criteria and mapping sets. The history is updated when the components are exported. , implementation_dba_data: XLA.XLA_AMB_COMPONENTS_H ,
Table: XLA_STAGING_COMPONENTS_H 12.1.1
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_STAGING_COMPONENTS_H, object_name:XLA_STAGING_COMPONENTS_H, status:VALID, product: XLA - Subledger Accounting , description: The XLA_STAGING_COMPONENTS_H table stores the history of the application accounting definitions and the non-application specific journal entry setups, i.e. analytical criteria and mapping sets, imported from the data file to the staging are , implementation_dba_data: XLA.XLA_STAGING_COMPONENTS_H ,
Table: XLA_STAGING_COMPONENTS_H 12.2.2
owner:XLA, object_type:TABLE, fnd_design_data:XLA.XLA_STAGING_COMPONENTS_H, object_name:XLA_STAGING_COMPONENTS_H, status:VALID, product: XLA - Subledger Accounting , description: The XLA_STAGING_COMPONENTS_H table stores the history of the application accounting definitions and the non-application specific journal entry setups, i.e. analytical criteria and mapping sets, imported from the data file to the staging are , implementation_dba_data: XLA.XLA_STAGING_COMPONENTS_H ,