Results for “fnd_id_flex_structures_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_ID_FLEX_STRUCTURES is the core definition table for Key Flexfield structures in Oracle E-Business Suite, owned by the APPLSYS schema within the FND — Application Object Library product. A key flexfield is a configurable, multi-segment field used throughout EBS to capture structured business entities such as Accounting Flexfields, Item Categories, and System Items. Each row in FND_ID_FLEX_STRUCTURES represents a single structure (a specific arrangement of segments) belonging to a particular key flexfield, uniquely identified by the combination of APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM. This table sits at the center of the flexfield definition model, serving as the parent for segments, validation rules, compiled structures, shorthand aliases, and a wide range of reporting and project accounting objects.

Based on the foreign key topology mined from the ETRM repository, the table is best modeled heuristically as a Data Vault hub. It holds the durable business key (APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM) that many dependent satellites and links reference, while descriptive attributes such as delimiter, freeze flags, and shorthand settings act as satellite-style payload.

Key Information Stored

The primary key, FND_ID_FLEX_STRUCTURES_PK, is defined over (APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM). Two unique indexes provide alternate business-key candidates: FND_ID_FLEX_STRUCTURES_U1 extends the PK with ZD_EDITION_NAME, and FND_ID_FLEX_STRUCTURES_U2 substitutes ID_FLEX_STRUCTURE_CODE, confirming that the structure code is also a unique business identifier. The most significant columns include:

• APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM — the composite business key identifying the owning application and flexfield structure.
• ID_FLEX_STRUCTURE_CODE — the developer-facing unique code for the structure, validated by the U2 unique index.
• ZD_EDITION_NAME — edition identifier supporting the multi-edition (ZD) data model introduced in EBS 12.2.
• CONCATENATED_SEGMENT_DELIMITER — the character used to join segments in concatenated display of the flexfield.
• CROSS_SEGMENT_VALIDATION_FLAG — indicates whether cross-segment validation rules are enforced.
• DYNAMIC_INSERTS_ALLOWED_FLAG — controls whether new segment value combinations may be created at runtime.
• ENABLED_FLAG — the standard FND enabled/disabled indicator governing whether the structure is active.
• FREEZE_FLEX_DEFINITION_FLAG — prevents modification of the flexfield definition.
• FREEZE_STRUCTURED_HIER_FLAG — prevents modifications to hierarchical structures.
• SHORTHAND_ENABLED_FLAG and SHORTHAND_LENGTH — govern use of shorthand aliases for rapid data entry.
• STRUCTURE_VIEW_NAME — the database view name generated for the compiled structure.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Because the user search referenced RG_REPORT_SETS, a frequent use case is tracing Financial Statement Generator (FSG) report sets back to the accounting flexfield structure they depend on. The RG_REPORT_SETS, RG_REPORTS, RG_REPORT_AXIS_SETS, and RG_REPORT_CONTENT_SETS tables all carry APPLICATION_ID, ID_FLEX_CODE, and (for RG_REPORTS) ID_FLEX_CODE_11I and STRUCTURE_ID as foreign references.

A representative query joins FSG report sets to their underlying structure:

• SELECT rs.report_set_name, fis.id_flex_code, fis.id_flex_num, fis.id_flex_structure_code FROM rg_report_sets rs JOIN fnd_id_flex_structures fis ON rs.application_id = fis.application_id AND rs.id_flex_code = fis.id_flex_code.

Other practical patterns include listing all enabled structures for a given flexfield (WHERE enabled_flag = 'Y'), inspecting delimiter and freeze settings before configuration changes, and determining the generated STRUCTURE_VIEW_NAME for direct SQL against compiled flexfield data. Administrators also query this table when troubleshooting segment validation, since FND_FLEX_VALIDATION_RULES and FND_FLEX_VALIDATION_RULE_STATS reference it directly.

Related Objects

The most significant related objects, per the documented foreign key relationships, are:

• FND_ID_FLEXS — parent table referencing this structure's APPLICATION_ID and ID_FLEX_CODE.
• FND_ID_FLEX_SEGMENTS — defines the individual segments belonging to each structure.
• FND_ID_FLEX_STRUCTURES_TL — translation table holding structure titles and descriptions.
• FND_COMPILED_ID_FLEX_STRUCTS — compiled runtime representation of each structure.
• FND_FLEX_VALIDATION_RULES and FND_FLEX_VALIDATION_RULE_STATS — cross-segment validation definitions and statistics.
• FND_SHORTHAND_FLEX_ALIASES — shorthand alias definitions keyed to the structure.
• RG_REPORTS, RG_REPORT_SETS, RG_REPORT_AXIS_SETS, RG_REPORT_CONTENT_SETS, RG_REPORT_REQUESTS, RG_ROW_ORDERS — FSG reporting objects referencing the accounting flexfield structure.
• PA_SEGMENT_RULE_PAIRINGS_ALL — Projects accounting segment rule pairings.
• FND_FLEX_WORKFLOW_PROCESSES — flexfield-related workflow configuration.