Search Results fnd_flex_values_uk1
Overview
The FND_FLEX_VALUES table is a core repository within the Oracle E-Business Suite Application Object Library (FND). It serves as the master table for storing all valid values for key flexfield and descriptive flexfield segments across the application. Every predefined code, identifier, or lookup that populates a flexfield segment—such as an Accounting Flexfield (GL_CODE_COMBINATIONS) value or an Item Category—is stored as a record in this table. Its role is central to ensuring data integrity and providing a controlled list of acceptable entries for critical business data points throughout the EBS modules.
Key Information Stored
The table's structure is designed to manage flexfield values within a hierarchical and value set-specific context. The primary identifier is the FLEX_VALUE_ID, a unique system-generated key. The FLEX_VALUE_SET_ID is a foreign key to FND_FLEX_VALUE_SETS, grouping values into distinct sets. The FLEX_VALUE column stores the actual code or value itself. A critical column for hierarchical relationships is PARENT_FLEX_VALUE_LOW. It, along with FLEX_VALUE_SET_ID and FLEX_VALUE, forms a unique key (FND_FLEX_VALUES_UK1). This column stores the parent value's FLEX_VALUE, enabling the construction of parent-child value hierarchies (e.g., a summary account being the parent of multiple detail accounts). Other important columns typically include ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE for controlling valid usage, and SUMMARY_FLAG to indicate if a value is a parent.
Common Use Cases and Queries
A primary use case is querying valid values for reporting or data validation. For example, to list all enabled values in a specific value set by name, along with their parent values, a developer might execute:
- SELECT fv.flex_value, fv.description, fv.parent_flex_value_low FROM fnd_flex_values_vl fv WHERE fv.flex_value_set_id = (SELECT flex_value_set_id FROM fnd_flex_value_sets WHERE flex_value_set_name = 'XXCUST_ACCOUNT_CODE') AND fv.enabled_flag = 'Y' ORDER BY fv.flex_value;
The PARENT_FLEX_VALUE_LOW column is specifically queried to traverse hierarchies, such as generating a tree of all child values under a given parent, or validating that a new value's proposed parent exists and is enabled within the same value set. It is also essential for APIs and programs that load or maintain hierarchical flexfield value data.
Related Objects
FND_FLEX_VALUES is intrinsically linked to several key objects. The FND_FLEX_VALUE_SETS table defines the sets to which values belong, enforced by a foreign key constraint. The FND_FLEX_VALUES_TL table holds the translated descriptions for the values, linked via FLEX_VALUE_ID. For specific implementations, it may be referenced directly by other tables, as indicated by the foreign key from JL_CO_GL_NIT_ACCTS (a country-specific localization table). In practice, most application code accesses values via the FND_FLEX_VALUES_VL view, which combines the base table with its translations. Key maintenance is often performed via the standard FND_FLEX_VALUES_PKG API.
-
Table: FND_FLEX_VALUES
12.1.1
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.FND_FLEX_VALUES, object_name:FND_FLEX_VALUES, status:VALID, product: FND - Application Object Library , description: Valid values for flexfield segments , implementation_dba_data: APPLSYS.FND_FLEX_VALUES ,
-
Table: FND_FLEX_VALUES
12.2.2
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.FND_FLEX_VALUES, object_name:FND_FLEX_VALUES, status:VALID, product: FND - Application Object Library , description: Valid values for flexfield segments , implementation_dba_data: APPLSYS.FND_FLEX_VALUES ,
-
eTRM - FND Tables and Views
12.2.2
description: No longer used ,
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,
-
eTRM - FND Tables and Views
12.2.2
description: No longer used ,
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,