Search Results fnd_natural_languages_u1

Overview

APPLSYS.FND_NATURAL_LANGUAGES is a seed data table in Oracle E-Business Suite that stores the set of natural (human) languages known to the application tier. It is the authoritative reference for language codes and their ISO equivalents, and it underpins the multilingual and globalization features that allow an EBS instance to operate in more than one language. The table is owned by the APPLSYS schema and is registered in the FND design data repository as FND.FND_NATURAL_LANGUAGES. Its storage characteristics are typical of a low-volume, read-mostly seed object: it resides in the APPS_TS_SEED tablespace with a PCTFREE of 10, and the object is reported as VALID in the 12.2.2 physical schema.

In a Data Vault modeling sense, this object is best characterized as a hub suggestion. The table holds a stable, non-volatile business key (the language code) together with descriptive attributes, and it is not dependent on any parent object. The ETRM dependency report confirms that FND_NATURAL_LANGUAGES does not reference any other database object, which is consistent with a standalone reference data entity rather than a transactional or junction table.

Key Information Stored

The table is defined by a small, focused column set. The most significant columns are:

• LANGUAGE_CODE (VARCHAR2, 30) — the language code, based on RFC 3066. This is the primary key of the table and the unique business-key candidate exposed through the FND_NATURAL_LANGUAGES_U1 unique index.
• ISO_LANGUAGE_3 — the alpha-3 language code per ISO-639-2.
• ISO_TERRITORY — the alpha-2 territory code per ISO-3166-1, used to distinguish regional variants of a language.
• ENABLED_FLAG — a flag indicating whether the language is enabled for use in the instance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns that record audit and version information for each row.
• ZD_EDITION_NAME — the edition name column, present in the 12.2.2 physical schema and part of the second unique index, FND_NATURAL_LANGUAGES_U1 (LANGUAGE_CODE, ZD_EDITION_NAME). This reflects the Edition-Based Redefinition (EBR) architecture introduced in EBS 12.2.

Note that the ETRM excerpt lists a single-column unique index on LANGUAGE_CODE, while the documented 12.2.2 physical schema identifies the unique index as a composite of LANGUAGE_CODE and ZD_EDITION_NAME. Both descriptions should be reconciled against the actual instance being investigated. Because the table is a standalone reference entity, no surrogate key beyond the natural language code is required.

Common Use Cases and Queries

Typical usage centers on validation, reporting, and globalization configuration. Common scenarios include verifying which languages are enabled in the instance, mapping RFC 3066 codes to their ISO-639-2 equivalents for external system integration, and driving language-specific sorting or display logic in reports.

To list all enabled languages:

SELECT LANGUAGE_CODE, ISO_LANGUAGE_3, ISO_TERRITORY
FROM   APPLSYS.FND_NATURAL_LANGUAGES
WHERE  ENABLED_FLAG = 'Y';

To resolve a specific language code to its ISO attributes:

SELECT LANGUAGE_CODE, ISO_LANGUAGE_3, ISO_TERRITORY, ENABLED_FLAG
FROM   APPLSYS.FND_NATURAL_LANGUAGES
WHERE  LANGUAGE_CODE = :language_code;

Because the table is a seed object, it is queried far more often than it is updated. Administrators generally do not modify it directly; language installation and enablement are performed through the AD administration utilities and the Oracle Applications Manager interface, which write to this table as part of the language configuration cycle.

Related Objects

The dependency data indicates that FND_NATURAL_LANGUAGES is a standalone object that does not reference other database objects. It is, however, referenced by the APPS synonym FND_NATURAL_LANGUAGES, which is the common access point for application code and ad hoc queries. The table is closely associated with the broader FND language and territory seed tables that share its schema and tablespace (APPS_TS_SEED), and its ISO columns align with the ISO language and territory reference sets used across EBS globalization features. Because no downstream foreign keys are documented, join patterns are typically driven by LANGUAGE_CODE matching the language code columns found in FND_LANGUAGES and related NLS configuration tables rather than by enforced referential constraints.