Search Results fnd_descriptive_flexs_tl_uk1

Overview

The FND_DESCRIPTIVE_FLEXS_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It stores translated, language-specific versions of the titles and other descriptive elements for Descriptive Flexfields (DFFs). A Descriptive Flexfield is a key extensibility feature that allows organizations to add custom attributes to standard Oracle application forms without programming. This table works in conjunction with its base table, FND_DESCRIPTIVE_FLEXS, which holds the primary definition. The TL (Translation) table enables the EBS application to present DFF titles and prompts in the language of the end-user's session, supporting the global, multi-language capabilities of the platform.

Key Information Stored

The table's primary purpose is to hold translated text for DFF metadata. Its structure is defined by a composite primary key that uniquely identifies each translation record. The key columns are APPLICATION_ID, which identifies the owning application; DESCRIPTIVE_FLEXFIELD_NAME, the internal name of the flexfield; and LANGUAGE, the language code (e.g., 'US' for American English). A critical column is TITLE, which stores the translated name of the flexfield as it appears to users. The table also includes standard translation table columns such as SOURCE_LANG, CREATED_BY, and LAST_UPDATE_DATE. A unique key constraint (FND_DESCRIPTIVE_FLEXS_TL_UK1) on APPLICATION_ID, TITLE, and LANGUAGE ensures title uniqueness within a language and application context.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to render DFF regions in the correct language. From an administrative or reporting perspective, common use cases include auditing DFF translations, identifying missing translations for a new language, or troubleshooting display issues. A typical query retrieves the translated title for a specific DFF in the session language.

• Sample Query: To find all translations for a specific DFF:
  SELECT LANGUAGE, TITLE FROM APPLSYS.FND_DESCRIPTIVE_FLEXS_TL WHERE APPLICATION_ID = 401 AND DESCRIPTIVE_FLEXFIELD_NAME = 'PER_PEOPLE_F';
• Reporting Use Case: Identifying DFFs that lack a translation in a target language (e.g., French 'F'):
  SELECT b.TITLE as base_title FROM FND_DESCRIPTIVE_FLEXS b WHERE NOT EXISTS (SELECT 1 FROM FND_DESCRIPTIVE_FLEXS_TL t WHERE t.APPLICATION_ID = b.APPLICATION_ID AND t.DESCRIPTIVE_FLEXFIELD_NAME = b.DESCRIPTIVE_FLEXFIELD_NAME AND t.LANGUAGE = 'F');

Related Objects

The FND_DESCRIPTIVE_FLEXS_TL table has a direct, dependent relationship with its parent base table, FND_DESCRIPTIVE_FLEXS. As documented, a foreign key constraint links the TL table's APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME columns to the corresponding columns in the base table. This ensures that every translation record references a valid, existing DFF definition. The table is integral to the broader Descriptive Flexfield metadata structure, which includes related tables such as FND_DESCR_FLEX_COLUMN_USAGES_TL (for column prompts) and FND_DESCR_FLEX_CONTEXTS_TL (for context prompts). Data is typically maintained via the Oracle Application Developer responsibility forms or related APIs, not via direct DML.