Search Results fnd_languages_u3

Overview

APPLSYS.FND_LANGUAGES is a foundational Oracle E-Business Suite reference table that stores information about languages and dialects installed or recognized by an EBS instance. Each dialect is persisted as a distinct row and treated as a unique language within the EBS data model. The table holds the language code (for example, 'en' for English), a numeric identifier, the language name (for example, 'American'), the territory in which the language is spoken (for example, 'America'), ISO language and territory symbols, the associated code set, and a flag indicating whether the language is installed and available for use. The object resides in the APPS_TS_SEED tablespace, is owned by APPLSYS, and is marked VALID in release 12.1.1 and 12.2.2. It is FND design data (FND.FND_LANGUAGES), and its role is that of a master reference source consumed across nearly every product family in the E-Business Suite, including multilingual (MLS) _TL tables, CRM, Procurement, Projects, and Financials.

From a Data Vault modeling perspective, the mined relationship structure classifies FND_LANGUAGES as a hub. It anchors a stable business key and is referenced by a very large number of dependent tables rather than being a transactional or attribute-history structure itself.

Key Information Stored

The table is defined with 17 documented columns. The most significant are:

• LANGUAGE_CODE — the business language code (such as 'en', 'fr', 'DE'); part of the primary key FND_LANGUAGES_PK.
• LANGUAGE_ID — the numeric surrogate identifier for the language; unique via FND_LANGUAGES_U3.
• NLS_LANGUAGE — the language name (for example, 'American'), unique via FND_LANGUAGES_U5.
• NLS_TERRITORY — the territory in which the language is spoken.
• ISO_LANGUAGE and ISO_LANGUAGE_3 — ISO two- and three-character language symbols.
• ISO_TERRITORY — the ISO symbol for the territory.
• NLS_CODESET — the character code set associated with the language.
• INSTALLED_FLAG — indicates whether the language is installed and usable; indexed non-uniquely by FND_LANGUAGES_N1.
• LOCAL_DATE_LANGUAGE and UTF8_DATE_LANGUAGE — language strings used to represent the month component of dates under local and UTF8 conventions.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — editioning discriminator present in the 12.2.2 documented physical schema.

The primary key is FND_LANGUAGES_PK (LANGUAGE_CODE). Three unique indexes act as business-key candidates: FND_LANGUAGES_U1 (LANGUAGE_CODE, ZD_EDITION_NAME), FND_LANGUAGES_U3 (LANGUAGE_ID, ZD_EDITION_NAME), and the index of interest to the searcher, FND_LANGUAGES_U5 (NLS_LANGUAGE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage includes enumerating installed languages for a multi-language deployment, resolving a language code to its display name, and identifying the base language set for translations. A common query returns only the languages active on the instance:

• SELECT LANGUAGE_CODE, NLS_LANGUAGE, NLS_TERRITORY FROM FND_LANGUAGES WHERE INSTALLED_FLAG = 'Y' ORDER BY NLS_LANGUAGE;
• Lookup by business key: SELECT LANGUAGE_ID FROM FND_LANGUAGES WHERE LANGUAGE_CODE = :code;
• Reverse lookup by name using FND_LANGUAGES_U5: SELECT LANGUAGE_CODE FROM FND_LANGUAGES WHERE NLS_LANGUAGE = :name;

BI Publisher and Oracle Reports frequently join this table to MLS _TL tables to translate stored LANGUAGE codes into human-readable descriptions. Inventory scripts compare the set of installed languages against FND_LANGUAGES to validate translation coverage for a given release.

Related Objects

FND_LANGUAGES is heavily referenced. Notable dependents identified through the FK relationship data include:

• FND_LANGUAGES_TL — the translated variant, joined on LANGUAGE_CODE.
• CSS_DEF_LANGUAGES_B — referenced via FND_LANGUAGES.LANGUAGE_ID → CSS_DEF_LANGUAGES_B, and itself references FND_LANGUAGES through CSS_DEF_LANGUAGES_B.FND_LANGUAGE_CODE.
• AP_TERMS_TL — payment terms translations, joined on LANGUAGE and SOURCE_LANG.
• FND_NEW_MESSAGES — joined on LANGUAGE_CODE for message localization.
• HZ_PARTIES and HZ_LOCATIONS — join on LANGUAGE / LANGUAGE_NAME for Trading Community data.
• FND_EXECUTABLES_TL, FND_REQUEST_SETS_TL, FND_CONC_PP_TEMPLATES_TL — Concurrent Manager metadata translations.
• OE_TRANSACTION_TYPES_TL, PON_AUCTION_HEADERS_ALL, PA_PROJECTS_ERP_EXT_TL, and AMS_* tables — representative of the far-reaching MLS and CRM dependencies across the suite.

Maintenance is generally performed only through the AD Administration / NLS installation utilities; direct DML against this seed table should be avoided in production instances.