Search Results iso_territory




Overview
Explore in AI Chat

Overview

FND_NATURAL_LANGUAGES_VL is a multilingual (ML) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered by the FND – Application Object Library product and is documented as a "multilingual view for natural language table." Its purpose is to present natural language definitions—the languages that EBS supports for its user interface, data storage, and translations—with translated display attributes (NAME and DESCRIPTION) resolved at runtime to the language of the current session.

Because Oracle EBS stores language-independent attributes in a base table and translated text in a companion "_TL" table, the "_VL" suffix denotes a view that joins the two while filtering the translation rows by the session language environment. FND_NATURAL_LANGUAGES_VL therefore behaves like a single, session-sensitive source of natural language data, which is convenient for concurrent programs, reports, forms, and integration code that must display language names in the user's own language. Its columns also include the ISO codes, most notably ISO_TERRITORY, which makes it relevant for interoperability with external systems that identify languages and territories by ISO standards.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through synonyms in the APPS schema:

The view text joins the two on LANGUAGE_CODE and restricts translation rows using T.LANGUAGE = USERENV('LANG'). It aliases the base table as "B" and the translation table as "T", projecting B.ROWID as ROW_ID alongside the base attributes and the translated text columns. Because USERENV('LANG') resolves to the current session language, a query returns only the single row per language code whose translation matches the runtime environment.

Key Columns

  • ROW_ID — the ROWID of the base-table row, exposed for identification and updatable-view behavior.
  • LANGUAGE_CODE — the EBS internal language identifier (for example, US or FR); the join key between base and translation records.
  • ISO_LANGUAGE_3 — the three-character ISO 639-2/639-3 language code, used for external-system interoperability.
  • ISO_TERRITORY — the ISO territory (country) code associated with the language; this is the column users most often search for when mapping EBS languages to ISO locale definitions.
  • ENABLED_FLAG — indicates whether the language is active and selectable in the installation.
  • NAME and DESCRIPTION — translated text describing the language, resolved from the _TL table in the session language.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit (WHO) columns inherited from the base table.

Common Use Cases and Queries

The view is typically queried to enumerate installed or enabled languages, to resolve ISO codes for interface files, or to drive LOVs and reports. Because it filters on the session language, results for NAME and DESCRIPTION vary by environment, which should be accounted for in multi-language reporting.

  • List enabled languages with their ISO codes: 
    SELECT language_code, iso_language_3, iso_territory, name
FROM   apps.fnd_natural_languages_vl
WHERE  enabled_flag = 'Y'
ORDER BY name;
  • Look up a language by ISO territory: 
    SELECT language_code, name
FROM   apps.fnd_natural_languages_vl
WHERE  iso_territory = 'US';
  • Resolve an ISO language code to the EBS language code for integration mapping: 
    SELECT language_code, iso_language_3, iso_territory
FROM   apps.fnd_natural_languages_vl
WHERE  iso_language_3 = 'FRA';

These queries return the translation row matching the current session language, so reports executed by users with different language settings may display different NAME values for the same LANGUAGE_CODE.