Search Results xla_analytical_sources_u1

Overview

XLA.XLA_ANALYTICAL_SOURCES is a transactional configuration table in the Oracle E-Business Suite Subledger Accounting (XLA) module. It stores the definitions that govern how analytical criteria are applied to accounting sources during the generation of subledger journal entries. In the Oracle EBS 12.1.1 and 12.2.2 architectures, XLA replaces the earlier transaction-based accounting engine, and this table forms part of the Accounting Methods Builder (AMB) metadata repository that drives rules-based accounting derivation.

The table resides in the XLA schema, uses the APPS_TS_TX_DATA tablespace, and is registered as FND Design Data XLA.XLA_ANALYTICAL_SOURCES. As the ETRM documentation states, access is restricted to standard Oracle Applications programs; direct DML is unsupported. Based on the foreign-key and column structure, the heuristic Data Vault classification is standalone, suggesting the table can be modeled independently rather than as a strict hub, link, or satellite requiring aggressive normalization. Its role is configuration rather than transactional fact storage, holding the mapping between analytical source definitions and their associated detail and criterion types.

Key Information Stored

The primary key is XLA_ANALYTICAL_SOURCES_PK, a composite surrogate key spanning AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, ANALYTICAL_DETAIL_CODE, ENTITY_CODE, EVENT_CLASS_CODE, APPLICATION_ID, SOURCE_CODE, SOURCE_TYPE_CODE, and SOURCE_APPLICATION_ID. This ten-column key uniquely identifies each analytical source definition row.

A second unique index, XLA_ANALYTICAL_SOURCES_U1, provides an alternative business-key candidate over AMB_CONTEXT_CODE, ANALYTICAL_DETAIL_CODE, ANALYTICAL_CRITERION_TYPE_CODE, ENTITY_CODE, EVENT_CLASS_CODE, APPLICATION_ID, SOURCE_CODE, SOURCE_TYPE_CODE, SOURCE_APPLICATION_ID, and ZD_EDITION_NAME (the editioning column introduced in the 12.2 Online Patching model). The most important columns include:

• AMB_CONTEXT_CODE – the Accounting Methods Builder context that scopes the definition.
• ANALYTICAL_CRITERION_CODE / ANALYTICAL_CRITERION_TYPE_CODE – the analytical criterion and its type.
• ANALYTICAL_DETAIL_CODE – the analytical criteria detail code.
• ENTITY_CODE / EVENT_CLASS_CODE – the subledger entity and event class scope.
• APPLICATION_ID / SOURCE_APPLICATION_ID – internal application identifiers for the owning and source applications.
• SOURCE_CODE / SOURCE_TYPE_CODE – the source and its type.
• ZD_EDITION_NAME – the editioning column supporting 12.2 patching.
• Standard who columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical use cases include auditing which analytical sources are configured for a given AMB context, troubleshooting subledger accounting rule derivation, and migrating configurations between instances. A representative query joins the source definition to its criterion:

• SELECT AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ENTITY_CODE, EVENT_CLASS_CODE, SOURCE_CODE FROM XLA.XLA_ANALYTICAL_SOURCES WHERE APPLICATION_ID = :app_id AND ZD_EDITION_NAME = 'ORA_EDITION';
• Reporting on distinct SOURCE_TYPE_CODE values grouped by ENTITY_CODE and EVENT_CLASS_CODE for configuration inventory.
• Filtering by AMB_CONTEXT_CODE to compare accounting method setups across environments.

Because the object is internal, queries should be read-only and used for investigative reporting only.

Related Objects

Although the metadata classifies this table as standalone with no explicit foreign keys, it conceptually references the following significant XLA objects through shared code columns:

• XLA_ANALYTICAL_CRITERIA – joined on ANALYTICAL_CRITERION_CODE and ANALYTICAL_CRITERION_TYPE_CODE.
• XLA_AMB_CONTEXTS – joined on AMB_CONTEXT_CODE.
• XLA_EVENT_CLASSES – joined on EVENT_CLASS_CODE and APPLICATION_ID.
• XLA_ENTITY_TYPES / XLA_SOURCES – joined on ENTITY_CODE and SOURCE_CODE.
• FND_APPLICATION – resolved via APPLICATION_ID and SOURCE_APPLICATION_ID.
• FND_USER – resolved via CREATED_BY and LAST_UPDATED_BY who columns.
• XLA_ACCOUNTING_PROGRAMS – the concurrent programs that consume these source definitions.