Search Results xtr_sys_language_pk

Overview

XTR_SYS_LANGUAGES_TL is a translation table owned by the XTR (Treasury) schema in Oracle E-Business Suite. It was originally created by Oracle on 16-AUG-96 and remains marked VALID in current releases, including EBS 12.1.1 and 12.2.2. The object stores translated display text for Treasury system UI elements — such as menu modules, canvas types, and individual item names — so that Treasury pages, blotter screens, and dealer-facing workspaces can present labels in the language of the logged-in user.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. In practical terms this suggests modeling XTR_SYS_LANGUAGES_TL as a satellite-like reference table keyed on a composite business key rather than as a hub or link. The table is self-contained: it captures descriptive text keyed by module, canvas, item, and installed language, without acting as a junction between other XTR entities.

Key Information Stored

The table carries 11 documented columns. Four of them form the primary key, XTR_SYS_LANGUAGE_PK:

• MODULE_NAME — the Treasury module (e.g., FX, MM, Debt) whose UI element is being labeled.
• CANVAS_TYPE — the Oracle Forms canvas or regional grouping within that module.
• ITEM_NAME — the specific field, button, or prompt being translated.
• LANGUAGE — the target language code for the translated string.

The unique index XTR_SYS_LANGUAGES_TL_U1 mirrors the same four columns (MODULE_NAME, CANVAS_TYPE, ITEM_NAME, LANGUAGE), confirming the composite business key and enforcing that at most one translation exists per label per language.

The remaining documented columns carry the payload and audit trail:

• SOURCE_LANG — the source language from which the current text was derived.
• TEXT — the translated label string displayed to the user.
• CREATED_BY, CREATION_DATE — standard who/when audit columns for row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the last-modified audit trio used by Oracle's WHO columns and concurrent programs.

Common Use Cases and Queries

The most common usage is retrieving the correct label for a given module, canvas, and item in a specific language. A typical query pattern is:

• Label lookup: SELECT TEXT FROM XTR.XTR_SYS_LANGUAGES_TL WHERE MODULE_NAME = :p_module AND CANVAS_TYPE = :p_canvas AND ITEM_NAME = :p_item AND LANGUAGE = USERENV('LANG');
• Coverage audit: count distinct ITEM_NAME values grouped by LANGUAGE to identify languages missing translations for a module.
• Change tracking: filter on LAST_UPDATE_DATE to report labels modified since a given date, supporting translation review cycles.
• Consistency check: join against FND_LANGUAGES to verify the LANGUAGE values correspond to installed languages.

Related Objects

Because the mined classification is standalone, the table has no documented foreign keys to other XTR entities. It is nonetheless referenced conceptually by the following:

• FND_LANGUAGES — supplies the valid LANGUAGE codes referenced by the LANGUAGE column.
• XTR_SYS_LANGUAGES — the base (non-TL) counterpart holding default-language metadata for the same module/canvas/item key.
• FND_APPLICATION — identifies the XTR application context for these labels.
• XTR_BLOTTERS / XTR_CANVAS_ITEMS — Treasury UI definitions whose item names align with ITEM_NAME values.

Administrators typically maintain this table through concurrent translation programs rather than direct DML, ensuring the WHO audit columns remain accurate.