Results for “fnd_flex_values_tl”

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

Overview

FND_FLEX_VALUES_TL is the translation table for the Oracle Application Object Library (FND) key flexfield and descriptive flexfield value repository. It is owned by the APPLSYS schema and exists in both Oracle E-Business Suite 12.1.1 and 12.2.2. Its singular purpose is to store the language-specific attributes of flexfield values defined in the base table FND_FLEX_VALUES, allowing multi-language deployments to present value descriptions and meanings in a user's session language.

In Data Vault modeling terms, the FK structure suggests this object is satellite-leaning. It carries descriptive, language-dependent attributes keyed to the parent flexfield value entity rather than introducing new business entities or relationships, which is characteristic of a satellite attached to the FND_FLEX_VALUES hub.

Key Information Stored

The table is keyed by the composite primary key FND_FLEX_VALUES_TL_PK, comprising FLEX_VALUE_ID and LANGUAGE. The FLEX_VALUE_ID column is also the foreign key to FND_FLEX_VALUES, linking each translated row to its parent value definition. A separate unique index, FND_FLEX_VALUES_TL_U1, includes FLEX_VALUE_ID, LANGUAGE, and ZD_EDITION_NAME, serving as a business-key candidate that supports edition-aware lookups.

The most significant descriptive columns are:

• FLEX_VALUE_ID — Surrogate identifier of the parent flexfield value; the defining component of the primary key and the FK to FND_FLEX_VALUES.
• LANGUAGE — The NLS language code identifying which translation this row contains.
• FLEX_VALUE_MEANING — The translated meaning of the flexfield value as presented to users.
• DESCRIPTION — The translated long description of the value.
• SOURCE_LANG — The language in which the value was originally authored, used during translation maintenance.
• ZD_EDITION_NAME — Edition identifier supporting Online Patching (adop) editioning in 12.2.x.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who-column auditing attributes.

Common Use Cases and Queries

Typical uses center on resolving value descriptions in the correct language for reporting, interfaces, and validation. A common pattern joins the translation table to the base table filtered by the session language:

• Reporting flexfield value meanings per language for financial or HR extract files.
• Validating that translations exist for all active values before go-live in a multi-language rollout.
• Finding values missing a translation in a given language.

Illustrative SQL:

SELECT v.FLEX_VALUE, t.FLEX_VALUE_MEANING, t.DESCRIPTION FROM FND_FLEX_VALUES v, FND_FLEX_VALUES_TL t WHERE v.FLEX_VALUE_ID = t.FLEX_VALUE_ID AND t.LANGUAGE = USERENV('LANG') AND v.ENABLED_FLAG = 'Y';

To detect gaps, query the base table with a NOT EXISTS against the translation table for a target language. Reports should generally fall back to the base-table description when no translation row exists.

Related Objects

The principal related objects include:

• FND_FLEX_VALUES — The base (untranslated) value table; joined on FND_FLEX_VALUES_TL.FLEX_VALUE_ID = FND_FLEX_VALUES.FLEX_VALUE_ID.
• FND_FLEX_VALUE_SETS — The value set that owns each value, reached via the parent value row.
• FND_FLEX_VALUE_NORM_HIERARCHY — Hierarchy rollup definitions that reference values.
• FND_FLEX_VALIDATION — Validation rules referencing flexfield values.
• FND_ID_FLEX_STRUCTURES — Key flexfield structures whose segments consume these values.
• FND_FLEX_VALUES_VL — The translated view exposing language-appropriate values to forms and reports.

These relationships make FND_FLEX_VALUES_TL central to any multilingual reporting or integration effort that must present flexfield values in the user's language.