Search Results fnd_id_flex_structures




The FND_ID_FLEX_STRUCTURES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a fundamental repository for storing metadata related to Key Flexfields (KFFs) and Descriptive Flexfields (DFFs). It defines the structural configuration of flexfields, which are customizable data fields used to capture and organize business-specific information. This table is part of the Oracle Application Object Library (FND) and serves as a backbone for flexfield implementation, validation, and rendering across modules like General Ledger, Inventory, and Human Resources.

Key Attributes of FND_ID_FLEX_STRUCTURES

  1. APPLICATION_ID: Identifies the Oracle application (e.g., GL, INV) owning the flexfield.
  2. ID_FLEX_CODE: A unique code representing the flexfield type (e.g., 'GL#' for Accounting Flexfield, 'MTLL' for Item Categories).
  3. ID_FLEX_NUM: A numeric identifier for the specific structure within a flexfield (e.g., multiple Accounting Flexfield structures for different ledgers).
  4. ENABLED_FLAG: Indicates whether the structure is active ('Y') or inactive ('N').
  5. FREEZE_FLAG: If set to 'Y', prevents modifications to the structure to maintain data integrity.
  6. STRUCTURE_VIEW_NAME: Specifies the database view used for querying segment values.
  7. SEGMENT_SEPARATOR: Defines the delimiter between segments (e.g., '-', '.') in concatenated values.
  8. CROSS_VALIDATION_FLAG: Controls whether cross-validation rules are enforced ('Y' or 'N').
  9. DYNAMIC_COMBINATION_FLAG: If 'Y', allows dynamic creation of new combinations without explicit setup.

Functional Role in Oracle EBS

The table plays a pivotal role in:
  • Flexfield Setup: Defines segment ordering, prompts, and validation rules via child tables (e.g., FND_ID_FLEX_SEGMENTS).
  • Data Integrity: Enforces structure-specific rules like segment lengths and value sets through relationships with FND_FLEX_VALUE_SETS.
  • Multi-Org Support: Enables structure variations across operating units via ID_FLEX_NUM assignments.
  • Reporting & Integration: The STRUCTURE_VIEW_NAME facilitates SQL queries against flexfield data.

Technical Implementation

In EBS 12.1.1/12.2.2, this table is accessed through:
  • APIs: FND_FLEX_KEYVAL for validation; FND_FLEX_EXT for extensibility.
  • Forms: Configured via Oracle Flexfield Administrator (Screenshot > Application Developer > Flexfield > Key).
  • Upgrades/Migrations: Preserved during EBS upgrades, but customizations may require revalidation.

Example Use Case

For an Accounting Flexfield (GL#):
  1. A structure with ID_FLEX_NUM=101 defines segments: Company, Cost Center, Account.
  2. SEGMENT_SEPARATOR='-' formats values as 01-1000-50000.
  3. CROSS_VALIDATION_FLAG='Y' ensures invalid combinations (e.g., Revenue account under a non-sales cost center) are blocked.

Best Practices

  • Audit ENABLED_FLAG and FREEZE_FLAG before modifications.
  • Leverage DYNAMIC_COMBINATION_FLAG judiciously to balance flexibility with control.
  • Reference Oracle Metalink Note 134789.1 for patch-related impacts.