Search Results fnd_compiled_id_flexs




Overview
Explore in AI Chat

Overview

The FND_COMPILED_ID_FLEXS table is a core technical repository within the Application Object Library (FND) of Oracle E-Business Suite (EBS). It stores compiled, runtime-ready metadata for key flexfields. Key flexfields are configurable data structures, such as the Accounting Flexfield (GL#) or Item Categories, that allow organizations to capture and segment information specific to their business. This table does not hold transactional data; instead, it contains the processed definition of a flexfield's structure, segments, and validation rules after compilation. Its primary role is to provide a highly optimized, denormalized source for the EBS application to rapidly render and validate key flexfield entry forms and reports, significantly improving performance compared to reading from the numerous base definition tables each time.

Key Information Stored

The table's structure is designed to capture the complete compiled state of a key flexfield definition for a specific version and language. The primary key uniquely identifies a compiled instance through a combination of APPLICATION_ID (e.g., 101 for General Ledger), ID_FLEX_CODE (the internal code for the flexfield, like 'GL#'), COMPILER_VERSION_NUM (a sequential number tracking compilation events), SEQUENCE (ordering within the compiled data), and LANGUAGE. Key columns include the COMPILER_VERSION_NUM, which is critical for identifying the most recent compilation, and the LANGUAGE column, which supports multilingual implementations. The SEQUENCE column allows the compiled data, which can be lengthy, to be stored across multiple rows. The actual compiled metadata—such as segment prompts, order, validation flags, and value set information—is stored in a CLOB or LONG column (typically named DATA, though not explicitly listed in the provided metadata), which contains the serialized definition.

Common Use Cases and Queries

The primary use case is performance optimization for flexfield rendering. Developers and DBAs may query this table to investigate flexfield compilation status or version history. A common query retrieves the latest compilation version for a specific flexfield to verify deployment or troubleshoot issues where form behavior does not match defined metadata. For example:

  • Identifying the latest compiler version: SELECT MAX(compiler_version_num) FROM fnd_compiled_id_flexs WHERE application_id = 101 AND id_flex_code = 'GL#';
  • Checking compiled flexfields for a module: SELECT id_flex_code, compiler_version_num, language FROM fnd_compiled_id_flexs WHERE application_id = 101;

Direct manipulation of this table is strongly discouraged. All updates should be performed via the standard flexfield administration forms, which trigger a recompilation process that regenerates the data in this table.

Related Objects

FND_COMPILED_ID_FLEXS has a direct foreign key relationship to the base definition table, FND_ID_FLEXS. This enforces referential integrity, ensuring every compiled flexfield references a valid base definition. The join is performed on the composite key of APPLICATION_ID and ID_FLEX_CODE. This table is the target for the compilation process sourced from numerous flexfield definition tables (e.g., FND_ID_FLEX_STRUCTURES, FND_SEGMENT_ATTRIBUTE_VALUES). At runtime, EBS application logic and underlying packages reference FND_COMPILED_ID_FLEXS to obtain the flexfield metadata. It is also closely related to the analogous table for descriptive flexfields, FND_COMPILED_DESCRIPTIVE_FLEXS.