Results for “fnd_flex_kff_seg_vset_v”

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

Overview

The FND_FLEX_KFF_SEG_V view, owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2), provides a consolidated, denormalized picture of the Key Flexfield (KFF) configuration across the entire application instance. Rather than requiring the developer or DBA to join six separate metadata tables, this view exposes the full hierarchy of flexfield definitions: the owning application, the key flexfield itself, its enabled structures, the segments defined for each structure, and the value set attached to each segment together with the value set's validation characteristics.

Because Key Flexfields underpin core EBS entities such as Accounting Flexfields (Chart of Accounts), Key Flexfield segments define the individual components reported in General Ledger, Human Resources, and other modules. FND_FLEX_KFF_SEG_V is therefore useful for reporting, integration, and diagnostics where the objective is to understand which value sets govern which segments of which structures. It is a read-only reporting view and is not intended for direct updates.

Underlying Base Objects

The view is defined over the following documented base objects, all resolved in the APPS schema:

• FND_APPLICATION_VL (view) — supplies the application name for the flexfield's owning application.
• FND_ID_FLEXS (synonym) — the key flexfield definition (title, description, code).
• FND_ID_FLEX_STRUCTURES_VL (view) — enabled structures belonging to each flexfield.
• FND_ID_FLEX_SEGMENTS (synonym) — segment definitions per structure.
• FND_FLEX_VALUE_SETS (synonym) — the value set attached to each segment.
• FND_FLEX_VALIDATION_TABLES (synonym) — validation table metadata (joined with an outer (+) join, so it is optional).

The join predicates enforce that only enabled structures (S.ENABLED_FLAG = 'Y') and enabled segments (SG.ENABLED_FLAG = 'Y') are returned, and the value set join uses SG.FLEX_VALUE_SET_ID = V.FLEX_VALUE_SET_ID. The outer join to FND_FLEX_VALIDATION_TABLES ensures segments whose value set has no validation table mapping are still reported.

Key Columns

• APPLICATION_ID / APPLICATION_NAME — the owning application of the flexfield.
• ID_FLEX_CODE / ID_FLEX_NAME — the key flexfield code (e.g., GL#) and its descriptive title.
• ID_FLEX_NUM / ID_FLEX_STRUCTURE_NAME / S.DESCRIPTION — the structure identifier and name.
• SEGMENT_NAME — the individual segment definition.
• FLEX_VALUE_SET_ID / PARENT_FLEX_VALUE_SET_ID — the value set and its parent hierarchy.
• VALIDATION_TYPE — how the value set is validated (Independent, Table, Dependent, etc.).
• SECURITY_ENABLED_FLAG — whether value set security is enforced.
• SUMMARY_ALLOWED_FLAG — from FND_FLEX_VALIDATION_TABLES, indicates whether summary (parent) accounts are permitted.

Common Use Cases and Queries

Typical scenarios include auditing which value sets back each Accounting Flexfield segment, verifying validation types for integration testing, and documenting KFF configuration during upgrades or migrations.

List accounting flexfield segments and their value sets:

SELECT application_name, id_flex_code, id_flex_structure_name,
       segment_name, flex_value_set_id, validation_type
FROM   fnd_flex_kff_seg_v
WHERE  id_flex_code = 'GL#'
ORDER  BY id_flex_structure_name, segment_name;

Identify segments with security enabled:

SELECT id_flex_code, segment_name, flex_value_set_id, security_enabled_flag
FROM   fnd_flex_kff_seg_v
WHERE  security_enabled_flag = 'Y';

Note that the view queries multiple FND metadata tables and returns one row per segment per structure; joins to transactional tables should be made on FLEX_VALUE_SET_ID or ID_FLEX_NUM, and results should be filtered by application and flexfield code to avoid unnecessary scans.