Search Results xla_descriptions_tl




Overview
Explore in AI Chat

Overview

XLA_DESCRIPTIONS_TL is a translation (TL) table owned by the XLA schema within Oracle E-Business Suite, and belongs to the Subledger Accounting (XLA) product family. Its documented purpose is to store translated information about descriptions used by the Subledger Accounting engine. Like all standard EBS _TL tables, it holds one row per language for a given descriptive entity, enabling multi-language presentation of subledger accounting description metadata across 12.1.1 and 12.2.2 environments.

The object is documented as a TABLE with VALID status and 14 physical columns in the 12.2.2 ETRM schema. Its documented primary key is XLA_DESCRIPTIONS_TL_PK, defined over APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, DESCRIPTION_CODE, and LANGUAGE. Two unique indexes are documented as business-key candidates: XLA_DESCRIPTIONS_TL_U1 (adding ZD_EDITION_NAME to the primary key set) and XLA_DESCRIPTIONS_TL_U2 (APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, NAME, LANGUAGE, ZD_EDITION_NAME).

The ETRM relationship data classifies this object heuristically as standalone — it neither participates as a hub nor as a link in a Data Vault sense. This should be read as a modeling suggestion: the table functions as a descriptive translation satellite keyed by (APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, DESCRIPTION_CODE, LANGUAGE) without a documented foreign-key dependency to a parent hub.

Key Information Stored

The documented 14 columns partition naturally into key attributes, payload attributes, and standard EBS audit columns.

  • Key columns: APPLICATION_ID identifies the owning application; AMB_CONTEXT_CODE scopes the description to an accounting methods builder context; DESCRIPTION_TYPE_CODE and DESCRIPTION_CODE together identify the description entity being translated; LANGUAGE identifies the language of the row and is part of the primary key.
  • Payload columns: NAME holds the translated short name, DESCRIPTION holds the translated descriptive text, and SOURCE_LANG records the language from which the translation was derived.
  • Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow the standard EBS who-column conventions.
  • Editioning column: ZD_EDITION_NAME participates in both documented unique indexes and reflects the 12.2.x editioning model.

The surrogate primary key is the XLA_DESCRIPTIONS_TL_PK composite listed above; XLA_DESCRIPTIONS_TL_U1 and XLA_DESCRIPTIONS_TL_U2 are the documented business-key candidates.

Common Use Cases and Queries

Typical uses include rendering subledger accounting descriptions in the session language, building multi-language reference reports, and verifying translation completeness for a given description code.

A simple lookup in the current language:

  • SELECT name, description FROM xla_descriptions_tl WHERE application_id = :app AND amb_context_code = :ctx AND description_type_code = :type AND description_code = :code AND language = USERENV('LANG');

Detecting missing translations across languages joins the base and TL rows on the key columns and filters where NAME or DESCRIPTION is null or absent. Reporting queries frequently join to the base XLA_DESCRIPTIONS table on the same composite key to compare base and translated values per LANGUAGE. Because ZD_EDITION_NAME is part of both unique indexes, 12.2.x queries should either constrain or group by it to avoid duplicate edition rows.

Related Objects

The metadata documents XLA_DESCRIPTIONS_TL as standalone with no FK links, but it naturally relates to the base translation-master tables in the same schema. The most significant associated objects are:

  • XLA_DESCRIPTIONS — the base (non-translated) description table, joined on APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, and DESCRIPTION_CODE.
  • XLA_DESCRIPTION_TYPES — reference for valid DESCRIPTION_TYPE_CODE values.
  • FND_APPLICATION — resolves APPLICATION_ID to an application name.
  • FND_LANGUAGES — validates LANGUAGE codes and default-language flags.
  • XLA_AMB_CONTEXTS — resolves AMB_CONTEXT_CODE to the accounting methods builder context.
  • XLA_SUBLEDGER_ACCOUNTING_PKG and related XLA PL/SQL APIs — consume translated description metadata for rendering.
  • FND_FLEX_VALUES_TL — parallel TL pattern for flex value translations, useful as a modelling reference.