Search Results rg_report_sets

Overview

The FND_ID_FLEX_STRUCTURES table is a core repository for key flexfield structure definitions within the Oracle E-Business Suite (EBS) Application Object Library. It stores the metadata that defines each unique structural instance of a key flexfield. A key flexfield, such as the Accounting Flexfield (GL#) or the Item Categories Flexfield (MCAT), can have multiple enabled structures to support different business requirements (e.g., different chart of accounts for different legal entities). This table holds the master definition for each of these structures, including its identification, descriptive attributes, and configuration flags. It serves as the central reference point for all structural metadata, upon which segment definitions, validation rules, and compiled runtime forms are built.

Key Information Stored

The table's primary key uniquely identifies a flexfield structure through a combination of APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM. The APPLICATION_ID and ID_FLEX_CODE columns link the structure to its parent flexfield definition in the FND_ID_FLEXS table. The ID_FLEX_NUM is the unique identifier for the specific structure within that flexfield. Other critical columns include STRUCTURE_VIEW_NAME, which defines the database view for the structure, and ENABLED_FLAG, which controls the structure's availability. The table also stores descriptive information like the STRUCTURE_IDENTIFIER (a short name) and CONCAT_SEGMENT_LABELS. Configuration columns such as FREEZE_FLAG, CROSS_VALIDATION_FLAG, and DYNAMIC_INS_FLAG govern the structure's behavior during data entry and maintenance.

Common Use Cases and Queries

This table is central to flexfield administration, reporting, and troubleshooting. A common use case is generating a list of all enabled structures for a specific flexfield, such as the Accounting Flexfield (ID_FLEX_CODE = 'GL#'), to understand the chart of accounts setup. Another critical scenario involves identifying structures referenced in custom reports or interfaces. Sample queries include retrieving structure details for analysis or joining with segment tables to get a complete picture of a flexfield's configuration.

• List all structures for a flexfield:
  SELECT application_id, id_flex_code, id_flex_num, structure_identifier, enabled_flag, freeze_flag
  FROM fnd_id_flex_structures
  WHERE id_flex_code = 'GL#'
  ORDER BY id_flex_num;
• Find structures by descriptive name:
  SELECT fifs.application_id, fifs.id_flex_code, fifs.id_flex_num, fifstl.description
  FROM fnd_id_flex_structures fifs, fnd_id_flex_structures_tl fifstl
  WHERE fifs.application_id = fifstl.application_id
  AND fifs.id_flex_code = fifstl.id_flex_code
  AND fifs.id_flex_num = fifstl.id_flex_num
  AND UPPER(fifstl.description) LIKE '%CORPORATE%'
  AND fifstl.language = USERENV('LANG');

Related Objects

As indicated by its extensive foreign key relationships, FND_ID_FLEX_STRUCTURES is a pivotal parent table. The FND_ID_FLEX_SEGMENTS table stores the detailed definition of each segment within a structure, directly dependent on this table. FND_COMPILED_ID_FLEX_STRUCTS holds the runtime, denormalized version of the structure for performance. Validation and workflow dependencies are managed through FND_FLEX_VALIDATION_RULES and FND_FLEX_WORKFLOW_PROCESSES. For multilingual support, descriptive translations are stored in FND_ID_FLEX_STRUCTURES_TL. The table is also referenced by reporting tools (RG_REPORTS) and other modules, such as Projects (PA_SEGMENT_RULE_PAIRINGS_ALL), demonstrating its integration across the EBS ecosystem.