Search Results fnd_languages_tl_u1

Overview

APPLSYS.FND_LANGUAGES_TL is the translation (TL) table that accompanies the FND_LANGUAGES base table in Oracle E-Business Suite. It stores the translated, user-facing description of each national dialect (language) known to the system, presented in every installed language. The object is owned by APPLSYS and carries the FND design data reference FND.FND_LANGUAGES_TL.

In EBS releases 12.1.1 and 12.2.2 the table resides in the APPS_TS_SEED tablespace, the standard location for seed and reference data, with PCTFREE 10. The structure follows the classic multilingual pattern: a language-independent code column combined with a LANGUAGE column that identifies the translation context of the DESCRIPTION text. A row exists for each dialect for each installed language. For example, the German dialect (LANGUAGE_CODE = 'D') is described as "German" when LANGUAGE = 'US' and as "Allemand" when LANGUAGE = 'F'.

Heuristically, mined from its foreign-key structure, the table leans toward a satellite classification in a Data Vault model: it hangs off the FND_LANGUAGES hub and holds descriptive, language-dependent attributes rather than relationships or events. This is offered as a modeling suggestion rather than a documented fact.

Key Information Stored

The table contains ten documented columns. The most significant are:

• LANGUAGE_CODE — the short code identifying the national dialect; part of the primary key FND_LANGUAGES_TL_PK and the foreign key to FND_LANGUAGES.
• LANGUAGE — the language in which the translated DESCRIPTION column is presented; the second component of the primary key.
• DESCRIPTION — the translated name of the dialect, up to 255 characters.
• SOURCE_LANG — the language whose text mirrors this row. If the text is not yet translated into LANGUAGE, changes made to the source-language row are reflected here as well.
• ZD_EDITION_NAME — the editioning column present in 12.2.2, which partitions the data across editions and participates in all uniqueness constraints.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns capturing audit history.

The surrogate primary key is FND_LANGUAGES_TL_PK on (LANGUAGE_CODE, LANGUAGE). Two business-key candidates are documented as unique indexes: FND_LANGUAGES_TL_U2 on (DESCRIPTION, LANGUAGE, ZD_EDITION_NAME) — the index literally searched for by the "fnd_languages_tl_u2" query — and FND_LANGUAGES_TL_U1 on (LANGUAGE_CODE, LANGUAGE, ZD_EDITION_NAME). Both reside in APPS_TS_SEED.

Common Use Cases and Queries

The table is used whenever an application must present a language list in the user's own language, and in reports that must display a translated dialect name rather than a code. Typical query patterns include:

• Resolving the description of a single dialect for a logged-in language:
  SELECT description FROM applsys.fnd_languages_tl WHERE language_code = :code AND language = :session_lang;
• Producing a complete picklist of dialects, sorted by translated description, by joining FND_LANGUAGES for the INSTALLED_FLAG and then FND_LANGUAGES_TL on LANGUAGE_CODE.
• Identifying rows awaiting translation, where the DESCRIPTION equals the source language text, by comparing SOURCE_LANG with LANGUAGE.

Note that EBS ships a FND_LANGUAGES_TL view in the APPS schema that joins the table to FND_LANGUAGES and exposes convenience columns; querying the view is generally preferred in concurrent programs and Forms. Direct DML should be avoided for seed rows outside a patch or seed-data maintenance script.

Related Objects

• APPLSYS.FND_LANGUAGES — the parent table; joined on FND_LANGUAGES_TL.LANGUAGE_CODE = FND_LANGUAGES.LANGUAGE_CODE.
• APPS.FND_LANGUAGES_TL — the APPS-synonym view that adds language-independent attributes through a join to FND_LANGUAGES.
• FND_LANGUAGES_TL_PK, FND_LANGUAGES_TL_U1, FND_LANGUAGES_TL_U2 — the primary and unique indexes enforcing key integrity, the last being the entry point most commonly searched by name.
• FND_TERRITORIES_TL / FND_CURRENCIES_TL — sibling translation tables that follow the same LANGUAGE_CODE/LANGUAGE model and are frequently queried together with this one when building locale, address, or reporting hierarchies.