Search Results xla_analytical_sources




Overview
Explore in AI Chat

Overview

The XLA_ANALYTICAL_SOURCES table is a Subledger Accounting (XLA) repository object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the assignment between an Analytical Criteria detail and the sources that supply values to that detail during subledger journal entry creation. Subledger Accounting uses analytical criteria to define the conditional logic that determines which accounting rules apply to a transaction. Each analytical criterion is decomposed into one or more analytical details, and each detail is resolved at runtime by evaluating one or more source values drawn from the transaction, event, or application context. XLA_ANALYTICAL_SOURCES is the intersection table that binds those details to their underlying sources, making it a configuration-time mapping rather than a transactional or balancing object.

Because the table only records assignments between two configuration concepts and carries no independent descriptive attributes beyond standard audit columns, the heuristic Data Vault classification mined from its foreign key structure identifies it as standalone. In Data Vault modeling terms it is best treated as a link-style association: the primary key columns together represent the relationship between an analytical criterion detail and a source, and no separate hub is implied by the documented FK metadata.

Key Information Stored

The primary key, XLA_ANALYTICAL_SOURCES_PK, is a composite surrogate spanning all ten business columns: 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.

  • AMB_CONTEXT_CODE — the Accounting Methods Builder context that scopes the criterion and its sources.
  • ANALYTICAL_CRITERION_CODE and ANALYTICAL_CRITERION_TYPE_CODE — identify the analytical criterion and whether it is a predefined or user-defined criterion type.
  • ANALYTICAL_DETAIL_CODE — the specific detail line within the criterion to which a source is assigned.
  • ENTITY_CODE and EVENT_CLASS_CODE — the subledger entity and event class whose transactions the criterion applies to.
  • APPLICATION_ID — the application owning the analytical configuration.
  • SOURCE_CODE, SOURCE_TYPE_CODE, and SOURCE_APPLICATION_ID — the source that provides the value, its type, and the application that owns the source definition.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY — standard audit columns.
  • ZD_EDITION_NAME — the edition identifier supporting the edition-based redefinition model introduced in 12.2.

The unique index XLA_ANALYTICAL_SOURCES_U1 covers the same business columns plus ZD_EDITION_NAME, confirming the pairing of detail to source is unique per edition.

Common Use Cases and Queries

Typical use cases include auditing which sources feed a given analytical criterion, diagnosing why an accounting rule did not fire because a required source had no value, and documenting the analytical configuration for a subledger migration. A representative query returns all sources for a criterion detail:

  • SELECT analytical_criterion_code, analytical_detail_code, source_code, source_type_code FROM xla_analytical_sources WHERE amb_context_code = :ctx AND entity_code = :entity AND event_class_code = :ec;
  • Join to the source definition tables on SOURCE_CODE, SOURCE_TYPE_CODE, and SOURCE_APPLICATION_ID to obtain source names and value types.
  • Filter by ZD_EDITION_NAME to isolate the active edition when running against a 12.2.2 database.

Related Objects