Search Results xtr_sys_languages_tl_u1

Overview

XTR.XTR_SYS_LANGUAGES_TL is a translated-language (TL) seed table owned by the XTR schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores language-specific display text for the system-defined components of the XTR (Financial Trade Repository / treasury) module, keyed by the module, canvas type, and item name to which the text belongs. Because it is a TL table, it holds one row per translatable attribute per installed language, with the LANGUAGE column identifying the linguistic context of each row and SOURCE_LANG recording the originating language of the base definition. The table resides in the APPS_TS_SEED tablespace and is formally classified as VALID and as FND Design Data.

From a heuristic Data Vault modeling perspective, the metadata suggests this object behaves as a satellite. Its composite key of module, canvas type, item name, and language describes a descriptive, language-dependent attribute set rather than an independent business entity or an associative link. Organizations should treat this as a modeling suggestion only; the physical implementation remains a conventional EBS seed table.

Key Information Stored

The table exposes 11 documented columns. The most significant are:

• MODULE_NAME — the logical module that owns the item; part of the business key.
• CANVAS_TYPE — the canvas or context classification (VARCHAR2(20)); part of the business key.
• ITEM_NAME — the individual item within the canvas (VARCHAR2(100)); part of the business key.
• LANGUAGE — the language of the stored text; the final business-key component.
• SOURCE_LANG — the language in which the item was originally defined.
• TEXT — the actual translated display text (VARCHAR2(100)).
• CREATED_BY, CREATION_DATE — standard audit stamping of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO-column audit stamping of the last modification.

The documented primary key is XTR_SYS_LANGUAGE_PK over (MODULE_NAME, CANVAS_TYPE, ITEM_NAME, LANGUAGE). The unique index XTR_SYS_LANGUAGES_TL_U1 mirrors this same four-column combination, confirming that this set is the business-key candidate that guarantees one translation per item per language. A second, non-unique index XTR_SYS_LANGUAGES_TL_N1 on LANGUAGE supports language-scoped filtering. No surrogate numeric identifier is documented, so the composite natural key serves as the primary identity — an important consideration for the user's search term referencing xtr_sys_languages_tl_u1.

Common Use Cases and Queries

Typical scenarios include retrieving the display text for all items in a given module/canvas for a specific language, auditing which translations exist, and validating that seed data has loaded for every installed language. A representative query filtered on a single language follows:

SELECT MODULE_NAME, CANVAS_TYPE, ITEM_NAME, TEXT
FROM   XTR.XTR_SYS_LANGUAGES_TL
WHERE  LANGUAGE = :p_language
AND    MODULE_NAME = :p_module;

To detect coverage gaps across languages, compare distinct LANGUAGE values against the base definitions, isolating items whose SOURCE_LANG lacks a matching translation. Because the table is flagged Oracle Internal Use Only, reporting should be read-only and driven through supported XTR programs rather than direct DML.

Related Objects

The metadata documents that XTR_SYS_LANGUAGES_TL references no other database object, and that it is referenced only by the object XTR_SYS_LANGUAGES_TL# within the XTR schema. No foreign-key relationships are recorded, consistent with its heuristic Data Vault classification as standalone. Consequently, joins to other XTR seed or transactional tables — such as the underlying base (non-TL) definition tables and the system-language lookup utilities that populate LANGUAGE and SOURCE_LANG — are logical rather than enforced, keyed on shared values of MODULE_NAME, CANVAS_TYPE, and ITEM_NAME. Administrators should rely on the documented unique index and primary key for identity when reconciling translations against those related seed sources.