Search Results fnd_id_flex_structures_tl




Overview
Explore in AI Chat

Overview

The FND_ID_FLEX_STRUCTURES_TL table is a core Application Object Library (FND) table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 architecture. It functions as a translation table, storing multilingual descriptions for Key Flexfield (KFF) structures. A Key Flexfield is a customizable data field that captures segments of information, such as an Accounting Flexfield for chart of accounts combinations. Each flexfield can have multiple structures (e.g., different accounting structures for different ledgers). This table holds the translated names and descriptions for these structures, enabling the EBS user interface to display structure information in a user's chosen language, a critical feature for global deployments. It is owned by the APPLSYS schema and is integral to the internationalization framework of the application.

Key Information Stored

The table stores translated textual attributes for flexfield structures, linked to its base table via key columns. The primary and unique keys define its data integrity rules. Key columns include APPLICATION_ID, which identifies the EBS product module owning the flexfield; ID_FLEX_CODE, specifying the flexfield itself (e.g., 'GL#' for Accounting); and ID_FLEX_NUM, identifying the specific structure number. The LANGUAGE column holds the ISO language code (e.g., 'US' for American English). The most critical user-facing column is ID_FLEX_STRUCTURE_NAME, which contains the translated name of the flexfield structure as seen by users. Other typical translation (TL) table columns, such as DESCRIPTION and SOURCE_LANG, are also present to store the translated description and the original language of the record, respectively.

Common Use Cases and Queries

This table is primarily accessed by the application's internal translation mechanisms and for reporting on flexfield setup across languages. Common scenarios include generating a list of all translated structure names for a specific flexfield, or troubleshooting missing translations. A typical query joins this table to its base table, FND_ID_FLEX_STRUCTURES, to retrieve both technical and descriptive information. For example, to see all structures for the Accounting Flexfield in French, one might use:
SELECT fs.id_flex_structure_code, tl.id_flex_structure_name, tl.description
FROM fnd_id_flex_structures fs, fnd_id_flex_structures_tl tl
WHERE fs.application_id = tl.application_id
AND fs.id_flex_code = tl.id_flex_code
AND fs.id_flex_num = tl.id_flex_num
AND tl.language = 'F'
AND fs.id_flex_code = 'GL#';
Data in this table is typically maintained via the "Define Key Flexfield Structures" form or related administration APIs, not via direct SQL manipulation.

Related Objects

This table has a direct and essential relationship with several key FND objects. Its primary relationship is with the base table FND_ID_FLEX_STRUCTURES, as defined by its foreign key constraint. This links each translation record to a specific flexfield structure. It is also closely related to other flexfield metadata tables, such as FND_ID_FLEXS and FND_SEGMENT_ATTRIBUTE_VALUES. From a programmatic standpoint, data in this table is accessed and maintained through public Application Programming Interfaces (APIs) in packages like FND_FLEX_KEYVAL and FND_FLEX_DF. Developers and administrators should always use these provided APIs, rather than direct DML, to ensure data integrity and proper caching behavior within the EBS application tier.