Search Results fnd_flex_values_tl




Overview
Explore in AI Chat

Overview

The FND_FLEX_VALUES_TL table is a core Application Object Library table within Oracle E-Business Suite (EBS) that stores translated descriptions for flexfield value sets. It is a child table to FND_FLEX_VALUES, enabling the multilingual support critical for global deployments. Its primary role is to allow a single flexfield value, defined in the base table, to have multiple descriptive names, each associated with a specific language code. This separation of the value code from its language-specific description is fundamental to the EBS architecture, ensuring that key flexfields, descriptive flexfields, and key report parameters display appropriately based on a user's session language in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to support the translation model. The primary key is a composite of FLEX_VALUE_ID and LANGUAGE, enforcing uniqueness of a translation per language for a given value. Key columns include FLEX_VALUE_ID, which is a foreign key to FND_FLEX_VALUES.FLEX_VALUE_ID, linking the translation to the actual value code. The LANGUAGE column stores the standard Oracle language code (e.g., 'US' for American English, 'KO' for Korean). The most critical data column is DESCRIPTION, which holds the translated text for the flexfield value in the specified language. Additional columns like SOURCE_LANG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE support the translation and auditing framework.

Common Use Cases and Queries

A primary use case is generating reports or building application logic that must respect the user's language preference. Developers query this table to retrieve the appropriate description for a set of flexfield values. A common SQL pattern joins FND_FLEX_VALUES_TL to its parent table and filters by the session's language, often using the NLS_LANGUAGE database session parameter or the FND_GLOBAL.APPS_INITIALIZE API context.

  • Sample Query for Value Set Values: SELECT fv.flex_value, fvtl.description FROM fnd_flex_values fv, fnd_flex_values_tl fvtl WHERE fv.flex_value_id = fvtl.flex_value_id AND fv.flex_value_set_id = :value_set_id AND fvtl.language = USERENV('LANG') ORDER BY fv.flex_value;
  • Translation Maintenance: Administrators use this table to seed, add, or update translations for new or existing flexfield values, often through the "Translate Flexfield Values" form or related APIs.
  • Data Validation: Queries are used to identify values missing translations for a target language or to audit translation completeness.

Related Objects

The most direct and critical relationship, as defined by the foreign key metadata, is with the FND_FLEX_VALUES table. FND_FLEX_VALUES_TL.FLEX_VALUE_ID references FND_FLEX_VALUES.FLEX_VALUE_ID. This object is also integral to the view FND_FLEX_VALUES_VL, which provides a complete, language-sensitive view of flexfield values by joining the base and translation tables. Key APIs that interact with or depend on this table include FND_FLEX_VAL_API and the underlying routines for maintaining flexfield values. Furthermore, all application modules that implement translatable flexfields—such as General Ledger's Accounting Flexfield (GL#) or Inventory's Item Categories—ultimately rely on the data stored in FND_FLEX_VALUES_TL for their multilingual user interfaces.