Search Results fnd_id_flex_segments_tl

Overview

The FND_ID_FLEX_SEGMENTS_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It stores the translated, language-specific descriptions and prompts for the segments that define Key Flexfields (KFFs) and Descriptive Flexfields (DFFs). These flexfields are fundamental to the EBS architecture, allowing organizations to extend and customize the application data model. While the base table, FND_ID_FLEX_SEGMENTS, holds the structural definition and seed data (typically in American English), the *_TL counterpart enables the multilingual display of segment names, prompts, and descriptions to users globally. Its existence is critical for the internationalization (i18n) and localization of EBS implementations, ensuring that flexfield structures are presented in the user's preferred language.

Key Information Stored

The table's structure is designed to map language-specific text to a unique flexfield segment definition. Its primary key is a composite of columns that identify a specific segment and a language. Key columns include APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM, which together identify the specific flexfield structure. The APPLICATION_COLUMN_NAME identifies the specific segment within that structure. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'D' for German). The most critical data columns are DESCRIPTION, which holds the translated name of the segment, and FORM_LEFT_PROMPT and FORM_ABOVE_PROMPT, which store the translated prompts used on application forms. Additional columns like LAST_UPDATE_DATE and LAST_UPDATED_BY support the standard EBS auditing framework.

Common Use Cases and Queries

This table is primarily accessed by the EBS application runtime to render flexfield prompts in the correct language. Common technical and reporting use cases involve auditing translations or troubleshooting display issues. A typical query retrieves all translations for a specific flexfield, such as the Accounting Flexfield (GL#):

• SELECT language, description, form_left_prompt FROM fnd_id_flex_segments_tl WHERE id_flex_code = 'GL#' AND application_column_name = 'SEGMENT1' AND id_flex_num = 101;

Another common pattern is to join with the base table to compare seed data with translations for a given language:

• SELECT b.segment_name, t.description, t.language FROM fnd_id_flex_segments b, fnd_id_flex_segments_tl t WHERE b.application_id = t.application_id AND b.id_flex_code = t.id_flex_code AND b.id_flex_num = t.id_flex_num AND b.application_column_name = t.application_column_name AND t.language = 'D';

Direct data manipulation (DML) on this table is strongly discouraged; translations should be managed through the official "Translate Flexfield" administrative function within the EBS front-end or via the FND_FLEX_LOADER_APIs.

Related Objects

FND_ID_FLEX_SEGMENTS_TL has a direct and mandatory relationship with its parent base table, FND_ID_FLEX_SEGMENTS, as defined by its foreign key constraint. This ensures every translation record corresponds to a valid segment definition. It is intrinsically linked to the broader flexfield definition tables, including FND_ID_FLEXS (header definition) and FND_ID_FLEX_STRUCTURES. For programmatic operations, the FND_FLEX_KEYVAL and FND_FLEX_LOADER_APIs reference the translated data. From a reporting perspective, developers often use the FND_FLEX_SEGMENTS_VL view, which is a union of the base and translation tables, providing a complete, language-aware record for each segment.