Search Results freeze_structured_hier_flag

Overview

FND_ID_FLEX_STRUCTURES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the header-level definition of every key flexfield structure registered in the Application Object Library, joining the language-independent base table with its translation table so that users see the structure name, description, and shorthand prompt in their session language. The "_VL" suffix denotes a "view with language," meaning the view resolves translations through USERENV('LANG') rather than returning every installed language row. This view is the standard entry point for reporting and integration code that must enumerate key flexfield structures — for example, the Accounting Flexfield, the Key Flexfield for item categories, or any custom key flexfield — without querying the underlying tables directly.

Underlying Base Objects

The view is defined over two synonyms in the APPS schema: FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_STRUCTURES_TL. FND_ID_FLEX_STRUCTURES supplies the language-independent definition columns, while FND_ID_FLEX_STRUCTURES_TL supplies the translatable attributes ID_FLEX_STRUCTURE_NAME, DESCRIPTION, and SHORTHAND_PROMPT. The join predicates are on APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM, and the translation row is filtered by T.LANGUAGE = USERENV('LANG'). Because the view combines a physical table row with its translation, it is a non-updatable join view and must never be used for DML; flexfield structures are maintained through the Key Flexfield Segments form. The primary surrogate key in this view is the composite of APPLICATION_ID, ID_FLEX_CODE, and ID_FLEX_NUM.

Key Columns

• APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM — the unique identifier of a structure; ID_FLEX_CODE identifies the flexfield (for example, GL# for Accounting), and ID_FLEX_NUM is the structure number.
• ID_FLEX_STRUCTURE_CODE / ID_FLEX_STRUCTURE_NAME — the internal code and the user-visible, translated structure name.
• CROSS_SEGMENT_VALIDATION_FLAG — indicates whether cross-segment validation rules (segment value security relationships and dependent value sets) are enforced for this structure; a value of Y enables validation across segments at data entry.
• DYNAMIC_INSERTS_ALLOWED_FLAG — controls whether new segment value combinations may be created on the fly during entry.
• ENABLED_FLAG — denotes whether the structure is active and available to users.
• FREEZE_FLEX_DEFINITION_FLAG, FREEZE_STRUCTURED_HIER_FLAG — indicate whether the flexfield definition or its structured hierarchy has been frozen to protect the compiled structure.
• CONCATENATED_SEGMENT_DELIMITER — the character used to join segments in concatenated segment views.
• SHORTHAND_ENABLED_FLAG, SHORTHAND_LENGTH, SHORTHAND_PROMPT — control and prompt text for shorthand entry of combinations.
• STRUCTURE_VIEW_NAME — the underlying database view (for example, GL_CODE_COMBINATIONS-style structures) that stores combinations for this structure.

Common Use Cases and Queries

Typical uses include validating that cross-segment validation is enabled before reconciling dependent segments, listing active structures for a given application, and driving metadata extracts for integrations that must map local flexfield structures to external systems.

SELECT application_id
     , id_flex_code
     , id_flex_num
     , id_flex_structure_name
     , cross_segment_validation_flag
     , enabled_flag
  FROM apps.fnd_id_flex_structures_vl
 WHERE id_flex_code = 'GL#'
   AND enabled_flag = 'Y'
 ORDER BY id_flex_num;

Because the view filters on USERENV('LANG'), multi-language environments automatically return names in the caller's language. Where cross-language consistency is required, query the base translation table directly against a fixed LANGUAGE value instead of relying on the session default.