Search Results fnd_languages_tl




Overview
Explore in AI Chat

Overview

FND_LANGUAGES_TL is the translation table for FND_LANGUAGES within the Oracle E-Business Suite Application Object Library (FND) product, owned by the APPLSYS schema. It stores the language-dependent descriptive text associated with each installed language, allowing the same underlying language record to present localized names and descriptions depending on the session language. In EBS 12.1.1 and 12.2.2 this object supports the Multi-Language Support (MLS) infrastructure, and the "_TL" suffix confirms its role as the translatable companion to a base table.

From a Data Vault modeling perspective, the ETRM heuristic classifies this table as satellite-leaning. Its primary key is composed of the parent business key (LANGUAGE_CODE) plus the language discriminator (LANGUAGE), and all descriptive attributes are non-key context, which is characteristic of a satellite orbiting the FND_LANGUAGES hub. The table is not a hub or link in the strict sense; it carries descriptive, language-specific payload rather than relationships.

Key Information Stored

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

  • LANGUAGE_CODE — The base language identifier, acting as a foreign key into FND_LANGUAGES and forming part of the composite primary key.
  • LANGUAGE — The MLS language discriminator indicating which session language the row's text applies to; combined with LANGUAGE_CODE it forms the primary key FND_LANGUAGES_TL_PK.
  • DESCRIPTION — The localized human-readable description of the language record.
  • SOURCE_LANG — The original source language used for translation purposes, standard in MLS tables.
  • ZD_EDITION_NAME — A partitioning/editioning column supporting the 12.2 online editioning feature, present in the unique indexes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

Regarding business keys, two unique indexes are documented: FND_LANGUAGES_TL_U1 (LANGUAGE_CODE, LANGUAGE, ZD_EDITION_NAME) is the primary business-key candidate, while FND_LANGUAGES_TL_U2 (DESCRIPTION, LANGUAGE, ZD_EDITION_NAME) enforces additional uniqueness on the descriptive text. There is no independent surrogate key; identity is derived from the natural composite of LANGUAGE_CODE and LANGUAGE.

Common Use Cases and Queries

Typical use cases include listing available languages with their localized descriptions, verifying translation coverage, and joining to session or installation metadata. A representative query retrieves the description for a given language code in a target language:

  • SELECT language_code, language, description FROM fnd_languages_tl WHERE language = 'US' AND language_code = 'US';
  • SELECT t.language_code, t.description FROM fnd_languages_tl t WHERE t.source_lang = 'US' ORDER BY t.language_code;
  • Reporting scenarios often join FND_LANGUAGES_TL back to FND_LANGUAGES to compare installed base flags against localized text.
  • Data validation checks count rows per LANGUAGE to confirm every installed language has a corresponding translation entry.

Because ZD_EDITION_NAME participates in the unique indexes in 12.2, queries spanning editions should filter or group on that column when reconciliation against 12.1.x results is required.

Related Objects

  • FND_LANGUAGES — The base table; joined on FND_LANGUAGES_TL.LANGUAGE_CODE = FND_LANGUAGES.LANGUAGE_CODE, the sole documented foreign key relationship.
  • FND_LANGUAGE_USES — Tracks where languages are used across products; complements language coverage analysis.
  • FND_TERRITORIES_TL — Sibling MLS translation table for territories, following the same modeling pattern.
  • FND_CURRENCIES_TL — Another MLS translation companion useful when building multi-language lookup reports.
  • FND_LANGUAGES_VL — The MLS view that exposes base and translation columns in a session-language-aware form.

Together these objects underpin Oracle EBS multi-language presentation and should be treated as a cohesive MLS family in any query strategy.