Search Results xla_analytical_dtls_tl




Overview
Explore in AI Chat

Overview

XLA_ANALYTICAL_DTLS_TL is a translation (TL) table owned by the XLA schema within the Oracle E-Business Suite Subledger Accounting module. Subledger Accounting provides the accounting engine that transforms raw subledger transactions into journal entries, and the analytical criteria framework allows administrators to define reusable conditions and detail attributes that drive how accounting rules are evaluated. This table stores the translated descriptive detail information associated with each Analytical Criterion definition, complementing the base XLA_ANALYTICAL_DTLS_B table which holds language-independent data. The "_TL" suffix indicates that rows are maintained per installed language, enabling multilingual descriptions within a single EBS instance.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. This suggests it is best understood as an independent descriptive structure that could be modeled as a satellite-like reference table, since no explicit foreign key dependencies were mined from the schema. The physical table contains 14 documented columns in the 12.2.2 ETRM schema and is marked VALID.

Key Information Stored

The table's identity is anchored by the primary key XLA_ANALYTICAL_DTLS_PK, composed of AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, ANALYTICAL_DETAIL_CODE, and LANGUAGE. A second unique index, XLA_ANALYTICAL_DTLS_TL_U1, adds ZD_EDITION_NAME to those same five columns and represents the strongest business-key candidate, incorporating the edition-tracking column used by the EBS editioning framework.

  • AMB_CONTEXT_CODE — identifies the application context that owns the analytical criterion detail; part of both the primary key and the business-key unique index.
  • ANALYTICAL_CRITERION_CODE — the analytical criterion to which the detail belongs.
  • ANALYTICAL_CRITERION_TYPE_CODE — classifies the criterion type for the associated detail.
  • ANALYTICAL_DETAIL_CODE — the unique detail identifier within the criterion.
  • LANGUAGE — the language code of the translated row, key to the TL design.
  • SOURCE_LANG — the source language from which the description was originally entered.
  • NAME — the translated name of the analytical detail.
  • DESCRIPTION — the translated descriptive text for the detail.
  • ZD_EDITION_NAME — the edition name supporting EBS edition-based redefinition.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row creation and modification.

Common Use Cases and Queries

Typical reporting scenarios include listing all analytical detail descriptions for a specific language, auditing who created or modified translated detail rows, or joining to the base table to present both language-dependent and language-independent attributes. The following pattern retrieves translated detail rows for a given context and criterion:

  • SELECT adtl.AMB_CONTEXT_CODE, adtl.ANALYTICAL_CRITERION_CODE, adtl.ANALYTICAL_DETAIL_CODE, adtl.NAME, adtl.DESCRIPTION FROM XLA_ANALYTICAL_DTLS_TL adtl WHERE adtl.LANGUAGE = USERENV('LANG') AND adtl.AMB_CONTEXT_CODE = :context;
  • Join to XLA_ANALYTICAL_DTLS_B on AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, and ANALYTICAL_DETAIL_CODE to combine translated and base data for a complete detail listing.
  • Filter on ZD_EDITION_NAME to isolate rows belonging to a specific edition when the instance is running editioning in 12.2.x.

These queries support configuration review, translation completeness checks, and migration validation between 12.1.1 and 12.2.2 environments.

Related Objects

Because the metadata classifies this table as standalone with no mined foreign keys, related objects are inferred from the analytical criteria framework and shared key columns. The most significant associated objects include:

  • XLA_ANALYTICAL_DTLS_B — the base (non-translated) table joined on AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, and ANALYTICAL_DETAIL_CODE.
  • XLA_ANALYTICAL_CRITERIA_B / XLA_ANALYTICAL_CRITERIA_TL — the parent analytical criterion definition tables sharing ANALYTICAL_CRITERION_CODE and ANALYTICAL_CRITERION_TYPE_CODE.
  • XLA_AMB_CONTEXTS — the ambiguity context definition referenced by AMB_CONTEXT_CODE.
  • FND_LANGUAGES — the language reference table validating the LANGUAGE and SOURCE_LANG values.

These relationships should be validated against the actual instance, as the documented metadata does not assert enforced foreign key constraints.