Search Results fnd_compiled_id_flex_structs

Overview

The FND_COMPILED_ID_FLEX_STRUCTS table is a core technical repository within the Application Object Library (FND) of Oracle E-Business Suite. It stores compiled, runtime-ready information about the structures of key flexfields. Key flexfields are configurable segments that allow organizations to capture and represent business-specific identifiers, such as part numbers or account codes. While base definition tables hold the configured metadata, this table contains the processed and optimized version of that data, which is directly utilized by the application's flexfield engine for efficient validation and display. Its existence is critical for performance, as querying pre-compiled structures is significantly faster than dynamically interpreting complex flexfield definition rules during transaction processing.

Key Information Stored

The table's structure is designed to uniquely identify and store the compiled attributes of a specific flexfield structure. Its primary key is a composite of several columns: APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM, COMPILER_VERSION_NUM, SEQUENCE, and LANGUAGE. This design ensures versioning and multilingual support for compiled structures. Key columns include APPLICATION_ID and ID_FLEX_CODE, which identify the owning application and the specific flexfield (e.g., 'GL#' for the Accounting Flexfield). The ID_FLEX_NUM pinpoints the exact structure number within that flexfield. The COMPILER_VERSION_NUM is crucial, as it allows the system to maintain different compiled versions, facilitating online patching and upgrades. The SEQUENCE column typically orders the compiled segment data, and LANGUAGE supports translated segment names and prompts. The table's rows hold the denormalized, executable definition of each segment within the structure.

Common Use Cases and Queries

Direct manipulation or querying of this table by functional users or custom code is uncommon, as access is typically managed through dedicated flexfield APIs. Its primary use case is for performance optimization by the E-Business Suite runtime. However, technical consultants may query it for diagnostic purposes to verify the compiled state of a flexfield structure, especially after a change. A sample query to list compiled structures for a specific flexfield would be:

• SELECT application_id, id_flex_code, id_flex_num, compiler_version_num, language FROM apps.fnd_compiled_id_flex_structs WHERE id_flex_code = 'GL#';

Another critical scenario involves comparing the COMPILER_VERSION_NUM across sessions or after applying a patch to understand which version of a compiled structure is active. Reporting directly against this table is rare; instead, standard flexfield views or descriptive flexfield APIs are the recommended interfaces for retrieving segment information for reports.

Related Objects

The FND_COMPILED_ID_FLEX_STRUCTS table has a direct foreign key relationship to the FND_ID_FLEX_STRUCTURES table, which holds the base configuration metadata for flexfield structures. The compilation process transforms data from FND_ID_FLEX_STRUCTURES and related definition tables (like FND_ID_FLEX_SEGMENTS) into the optimized format stored in FND_COMPILED_ID_FLEX_STRUCTS. It is intrinsically linked to the flexfield compiler engine within the FND_FLEX_KEYVAL and FND_FLEX_DESC APIs, which are responsible for validating and describing flexfield values. For most functional operations, developers and administrators interact with public views such as FND_ID_FLEX_STRUCTURES_VL rather than this underlying compiled table.