Search Results fnd_id_flexs

Overview

The FND_ID_FLEXS table is a core repository table within the Application Object Library (FND) of Oracle E-Business Suite (EBS). It serves as the central registry for all Key Flexfields (KFFs) defined across the application. A Key Flexfield is a customizable data structure, such as the Accounting Flexfield (GL#) or the Item Categories Flexfield, that allows organizations to capture and represent business identifiers in a tailored manner. This table stores the high-level registration and definitional metadata for each flexfield, establishing its fundamental properties and linking it to the application database objects it utilizes. Its role is foundational; the data in FND_ID_FLEXS is referenced by numerous other flexfield-related tables to govern structure, validation, and compilation.

Key Information Stored

The table's primary columns define the flexfield's identity, application context, and physical implementation. The APPLICATION_ID and ID_FLEX_CODE columns together form the primary key, uniquely identifying a specific flexfield within the EBS instance. The ID_FLEX_NAME provides the internal name. Critical implementation columns include TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME, which specify the application and name of the database table where the flexfield's concatenated segment values (the "code combination") are physically stored. Other significant columns describe the flexfield's behavior, such as ENABLED_FLAG (active status), FREEZE_FLEX_DEFINITION_FLAG (lock for changes), and columns controlling the structure and segment entry forms.

Common Use Cases and Queries

This table is essential for technical analysis, troubleshooting, and generating flexfield metadata reports. Common scenarios include identifying all registered key flexfields within a module, diagnosing issues related to flexfield setup, and scripting configuration audits. A fundamental query retrieves the basic registration for a known flexfield, such as the Accounting Flexfield:

• SELECT application_id, id_flex_code, id_flex_name, application_table_name, enabled_flag FROM fnd_id_flexs WHERE id_flex_code = 'GL#' AND application_id = 101;

Another typical use case is listing all key flexfields along with their base tables for a given application:

• SELECT fif.id_flex_code, fif.id_flex_name, fif.application_table_name, fa.application_name FROM fnd_id_flexs fif, fnd_application fa WHERE fif.application_id = fa.application_id AND fif.application_id = &APPL_ID ORDER BY 1;

Related Objects

FND_ID_FLEXS has a central relationship with numerous other flexfield metadata tables, as documented by its foreign keys. Key dependent objects include:

• FND_ID_FLEX_STRUCTURES: Stores the individual structures (e.g., "Corporate", "Vision Operations") defined for a flexfield. Joined on APPLICATION_ID and ID_FLEX_CODE.
• FND_COMPILED_ID_FLEXS: Contains runtime, compiled metadata for performance. Joined on APPLICATION_ID and ID_FLEX_CODE.
• FND_SEGMENT_ATTRIBUTE_TYPES: Holds the definition of segment qualifiers (e.g., Cost Center, Account) available for the flexfield. Joined on APPLICATION_ID and ID_FLEX_CODE.
• FND_APPLICATION: Provides the application name for the APPLICATION_ID.
• FND_TABLES: Validates the TABLE_APPLICATION_ID and APPLICATION_TABLE_NAME combination.
• FND_FLEXBUILDER_FUNCTIONS and PA_FUNCTIONS: Associate specific functionality or processes with the flexfield.