Results for “fnd_languages”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_LANGUAGES is the Application Object Library (FND) reference table that stores the set of national dialects and language definitions recognized by an Oracle E-Business Suite instance. In Oracle EBS 12.1.1 and 12.2.2, it is owned by the APPLSYS schema, is documented as VALID, and physically contains 17 columns. The table functions as the central linguistic lookup: every translatable (TL) table and every attribute that captures a language value resolves its code against FND_LANGUAGES. Because virtually all multilingual and territory-specific features — including NLS settings, ISO codes, and date-language formatting — depend on it, the table is effectively the seed data map for the entire localization layer of EBS.

Under the heuristic Data Vault classification mined from the foreign key structure, FND_LANGUAGES behaves as a hub — a stable, non-transactional reference entity keyed on a durable business code, with a large fan-out of dependent satellites and links. This is a modeling suggestion rather than a mandate; in conventional relational terms it is a parent/master table. It is closely associated with FND_LANGUAGES_TL, which supplies the translated language names, and with FND_LANGUAGES_B-style usage patterns common to EBS NLS design.

Key Information Stored

The primary key is FND_LANGUAGES_PK, defined on LANGUAGE_CODE. A second unique key, FND_LANGUAGES_UK2, is defined on LANGUAGE_ID. In the documented 12.2.2 schema, three additional unique indexes serve as business-key candidates and include the ZD_EDITION_NAME discriminator: FND_LANGUAGES_U1 (LANGUAGE_CODE, ZD_EDITION_NAME), FND_LANGUAGES_U3 (LANGUAGE_ID, ZD_EDITION_NAME), and FND_LANGUAGES_U5 (NLS_LANGUAGE, ZD_EDITION_NAME). The presence of ZD_EDITION_NAME indicates support for edition-based multiple-language/edition records. The most significant columns include:

• LANGUAGE_CODE — the surrogate/business identifier and primary key value used across all referencing tables.
• LANGUAGE_ID — numeric surrogate key, unique, used internally by EBS and referenced by CSS_DEF_LANGUAGES_B.FND_LANGUAGE_CODE.
• NLS_LANGUAGE — the NLS language component used to build the NLS_LANG setting and drive session locale.
• NLS_TERRITORY — the territory component paired with the language for locale and date/number formatting.
• ISO_LANGUAGE and ISO_TERRITORY — two-letter ISO codes for interoperability and external interfaces.
• ISO_LANGUAGE_3 — the three-letter ISO language code.
• NLS_CODESET — the character set associated with the language, governing encoding for that dialect.
• INSTALLED_FLAG — indicates whether the language is actually installed/active in the instance.
• LOCAL_DATE_LANGUAGE and UTF8_DATE_LANGUAGE — date-language strings used for localized date rendering in database and UTF8 sessions.
• ZD_EDITION_NAME — the edition discriminator that appears in the composite unique keys.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-audit columns maintained on all reference tables.

Common Use Cases and Queries

FND_LANGUAGES is most commonly joined to explain or filter language codes returned by TL tables. A frequent reporting pattern retrieves translated language names by joining through FND_LANGUAGES_TL on LANGUAGE_CODE. A second common pattern drives NLS setup reviews, selecting English/ISO descriptions for active dialects. Because the user query that surfaced this object was "pa_res_formats_tl," a practical query links PA_RES_FORMATS_TL to FND_LANGUAGES to resolve its LANGUAGE and SOURCE_LANG columns to readable names.

• Resolving a TL row's language: SELECT f.LANGUAGE_CODE, f.NLS_LANGUAGE, f.ISO_LANGUAGE FROM FND_LANGUAGES f, PA_RES_FORMATS_TL t WHERE t.LANGUAGE = f.LANGUAGE_CODE.
• Listing installed dialects: SELECT LANGUAGE_CODE, NLS_LANGUAGE, NLS_TERRITORY FROM FND_LANGUAGES WHERE INSTALLED_FLAG = 'Y'.
• Locale/NLS reporting: selecting NLS_LANGUAGE, NLS_TERRITORY, NLS_CODESET for a given LANGUAGE_CODE to validate session locale configuration.
• Filtering multilingual source rows by source language via SOURCE_LANG joined back to this hub.

Related Objects

The table is referenced by an extensive fan-out of TL tables and functional tables. The most significant relationships evidenced in the FK metadata are:

• PA_RES_FORMATS_TL — references FND_LANGUAGES via LANGUAGE and SOURCE_LANG (the object in the originating search).
• AP_TERMS_TL — payment terms translations, joining on LANGUAGE and SOURCE_LANG.
• FND_LANGUAGES_TL — the translated-names satellite referencing LANGUAGE_CODE.
• HZ_PARTIES / HZ_PERSON_LANGUAGE — reference LANGUAGE_NAME for party and person language attributes.
• OE_TRANSACTION_TYPES_TL — order transaction type translations via LANGUAGE.
• PON_AUC_DOCTYPES_TL and other PON TL tables — sourcing and sourcing-language lookups.
• CSS_DEF_LANGUAGES_B — references FND_LANGUAGES through FND_LANGUAGE_CODE, and is conversely referenced by LANGUAGE_ID.
• GR_*_TL tables — the Oracle Grants/regulatory multilingual set joining on LANGUAGE and SOURCE_LANG.

Collectively, these dependencies confirm FND_LANGUAGES' role as the linguistic hub underpinning NLS, translation (TL), and territory-aware processing across the EBS 12.1.1 and 12.2.2 schemas.