Results for “fnd_id_flex_structures_tl”

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

Overview

FND_ID_FLEX_STRUCTURES_TL is the translation table for FND_ID_FLEX_STRUCTURES in Oracle E-Business Suite, owned by the APPLSYS schema and delivered under the FND – Application Object Library product. The base table stores the structural definition of a key flexfield — its owning application, the flexfield code, and an internal structure number — while this companion table holds the language-dependent descriptive attributes that accompany each structure, most notably the user-visible structure name and description. Because a key flexfield structure must be presented to users in their own language, translated names are maintained separately from the language-independent definition, and this table is the mechanism Oracle uses to hold that translated content.

From a modeling perspective, the ETRM metadata classifies this object heuristically as satellite-leaning. Under a Data Vault interpretation, the business key (application, flexfield code, structure number) identifies the parent structure as a hub-like entity, and this table acts as a satellite carrying the descriptive, language-qualified attributes. The classification is a modeling suggestion rather than a physical identity; in EBS itself the table is simply a normalization and translation pattern layered on FND_ID_FLEX_STRUCTURES.

Key Information Stored

The most consequential columns in this table are:

• APPLICATION_ID — the application that owns the key flexfield; part of the compound primary key and the foreign key back to FND_ID_FLEX_STRUCTURES.
• ID_FLEX_CODE — the short code identifying the key flexfield (for example the code for Accounting Flexfield); also part of the key.
• ID_FLEX_NUM — the internal number distinguishing one structure from another within the same flexfield.
• LANGUAGE — the language of the translated row; combines with the three preceding columns to form FND_ID_FLEX_STRUCTURES_TL_PK.
• ID_FLEX_STRUCTURE_NAME — the translated, user-facing name of the structure; it participates in the unique index FND_ID_FLEX_STRUCTURES_TL_UK1 (APPLICATION_ID, ID_FLEX_CODE, LANGUAGE, ID_FLEX_STRUCTURE_NAME), acting as a business-key candidate that enforces name uniqueness within a language.
• DESCRIPTION — the translated descriptive text for the structure.
• SHORTHAND_PROMPT — the abbreviated prompt used when the flexfield structure is displayed in a condensed form.
• SOURCE_LANG — indicates the language in which the row was originally entered, supporting Oracle's translation and language-derivation logic.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 schema, participating in the unique index FND_ID_FLEX_STRUCTURES_TL_U1; it reflects the online editioning framework introduced in that release and is not relevant on 12.1.1.
• The standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record row provenance and change history.

The surrogate primary key is therefore FND_ID_FLEX_STRUCTURES_TL_PK over (APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, LANGUAGE), while FND_ID_FLEX_STRUCTURES_TL_UK1 provides the business-key candidate on the translated name.

Common Use Cases and Queries

The table is used principally for multilingual reporting and for resolving the display name of a flexfield structure when building configuration or validation extracts. A typical query joins the translation table to its base table on APPLICATION_ID, ID_FLEX_CODE and ID_FLEX_NUM, filtered by LANGUAGE to return the correct localized name. Reporting extracts commonly join onwards to FND_ID_FLEX_SEGMENTS to obtain segment definitions alongside the translated structure name.

Sample pattern (name-holding derivation):

• Join condition: FND_ID_FLEX_STRUCTURES_TL.APPLICATION_ID = FND_ID_FLEX_STRUCTURES.APPLICATION_ID, ID_FLEX_CODE = ID_FLEX_CODE, ID_FLEX_NUM = ID_FLEX_NUM.
• Restrict on TL.LANGUAGE = 'US' (or the target language) to obtain one row per structure.
• Select ID_FLEX_STRUCTURE_NAME, DESCRIPTION and SHORTHAND_PROMPT for presentation, and use SOURCE_LANG when auditing which language the content originated from.

Migration and comparison projects frequently compare row counts between the base and translation tables to detect structures that have not yet been translated, and compare UK1 name collisions per language.

Related Objects

The principal related objects are:

• FND_ID_FLEX_STRUCTURES — the parent, language-independent definition; this table's foreign key references it through APPLICATION_ID, ID_FLEX_CODE and ID_FLEX_NUM.
• FND_ID_FLEX_SEGMENTS — stores segment columns for each structure and is joined on the same structure key for full key flexfield reporting.
• FND_ID_FLEXS — holds flexfield-level attributes and provides the DESCRIPTION for the owning application.
• FND_APPLICATION / FND_APPLICATION_TL — supplies the owning application name for cross-application reports.
• FND_FLEX_VALIDATION_TABLES / FND_FLEX_VALUES — depends on structures for value set and validation configuration in key flexfield setup.
• FND_SEGMENT_ATTRIBUTE_VALUES — stores segment-level qualifier information associated with structures.

Standard API access to structure definitions, including translation maintenance, is provided through the FND_FLEX_KEY_API (and the key flexfield structure API), which is the supported route for creating or updating structures rather than direct DML against these tables.