Results for “fnd_id_flex_segments_tl_pk”

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

Overview

FND_ID_FLEX_SEGMENTS_TL is the translation (language) table for the Oracle EBS Key Flexfield segment definitions stored in FND_ID_FLEX_SEGMENTS. It resides in the APPLSYS schema and belongs to the FND – Application Object Library product. Because EBS is a multi-language application, descriptive and user-facing text such as segment prompts and segment descriptions is not held in a single base table; instead, the translatable attributes are split into a "_TL" companion table so that each installed language can present the same segment definition with its own localized wording. Every row corresponds to one segment of one key flexfield structure in one language.

From a data-modeling perspective, the metadata's heuristic classification of this object is satellite-leaning. This reflects the pattern in which FND_ID_FLEX_SEGMENTS acts as the driving (parent) entity keyed by the flexfield identity, while the _TL table carries the language-dependent descriptive attributes attached to that identity. The suggestion is a modeling hint rather than an enforced constraint.

Key Information Stored

The table is keyed by a composite primary key, FND_ID_FLEX_SEGMENTS_TL_PK, defined over the following columns:

• APPLICATION_ID – the application owning the key flexfield (e.g., the owning product of the flexfield).
• ID_FLEX_CODE – the key flexfield code, such as GL# for the Accounting Flexfield.
• ID_FLEX_NUM – the internal structure (definition) number that identifies the specific flexfield structure.
• APPLICATION_COLUMN_NAME – the segment's column name within the flexfield (for example SEGMENT1).
• LANGUAGE – the language code for which the translated text applies.

Together these five columns form the primary key. Note that a documented unique index, FND_ID_FLEX_SEGMENTS_TL_U1, extends the same set of columns with ZD_EDITION_NAME, indicating the business-key candidate carries an edition qualifier in the 12.2.2 data model. The translatable payload consists of the user-facing text attributes:

• FORM_LEFT_PROMPT – the label displayed to the left of the segment field on the flexfield entry form.
• FORM_ABOVE_PROMPT – the label displayed above the segment field where a stacked prompt layout is used.
• DESCRIPTION – the descriptive text for the segment.
• SOURCE_LANG – identifies the source language from which the translation was derived.

Standard WHO audit columns are also present, specifically LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent requirement is to report the prompt and description text of a flexfield's segments in a specific language. A typical query joins the translation table to its base table on the shared key columns and filters by language:

SELECT s.application_column_name, t.form_left_prompt, t.form_above_prompt, t.description FROM applsys.fnd_id_flex_segments s, applsys.fnd_id_flex_segments_tl t WHERE s.application_id = t.application_id AND s.id_flex_code = t.id_flex_code AND s.id_flex_num = t.id_flex_num AND s.application_column_name = t.application_column_name AND t.language = 'US';

Other uses include verifying that localized prompts exist for every installed language (a completeness audit), troubleshooting blank or incorrect prompts on a flexfield entry form, and extracting segment descriptions for documentation or data-migration work. Because the table is keyed by language, scripts that bulk-load flexfield metadata must insert one _TL row per active language.

Related Objects

• FND_ID_FLEX_SEGMENTS – the parent base table holding the language-independent segment definition. It is joined on APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, and APPLICATION_COLUMN_NAME, which are the documented foreign-key columns from the _TL table.
• FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_STRUCTURES_TL – the flexfield structure definition and its translations, which contextualize ID_FLEX_NUM and ID_FLEX_CODE.
• FND_ID_FLEXS – the flexfield registration table that defines the ID_FLEX_CODE values referenced here.
• FND_APPLICATION – provides the application name for APPLICATION_ID.
• FND_LANGUAGES – the installed language list that constrains valid LANGUAGE values.

These objects are commonly queried together to present a complete, localized picture of a key flexfield's structure and segments.