FND_FLEX_VALUES
Schema: APPLSYScontrolThe valid values belonging to each flexfield value set — one row per segment value, with enabled/date-effectivity flags and the parent-value linkage dependent and rollup hierarchies use
The value's description text is NOT on this table — it lives on the translation companion (FND_FLEX_VALUES_TL, not yet cataloged), so a description join is language-filtered.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
10 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | FLEX_VALUE_ID | Surrogate key of the flexfield value | NUMBER | Key |
| 2 | FLEX_VALUE_SET_ID | The value set this value belongs to — joins to FND_FLEX_VALUE_SETS | NUMBER | |
| 3 | FLEX_VALUE | The stored segment value itself | VARCHAR2 | |
| 4 | ENABLED_FLAG | Whether the value is active | VARCHAR2 | |
| 5 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 6 | END_DATE_ACTIVE | Effectivity end date | DATE | |
| 7 | SUMMARY_FLAG | Whether this is a summary (rollup) value rather than a postable detail value | VARCHAR2 | |
| 8 | PARENT_FLEX_VALUE_LOW | Parent value for dependent value sets — the independent value this row is valid under | VARCHAR2 | |
| 9 | VALUE_CATEGORY | Descriptive-flexfield context category on the value | VARCHAR2 | |
| 10 | STRUCTURED_HIERARCHY_LEVEL | Hierarchy level for structured value sets | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading FND_FLEX_VALUESon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : FND_FLEX_VALUES — The valid values belonging to each flexfield value set — one row per segment value, with enabled/date-effectivity flags and the parent-value linkage dependent and rollup hierarchies use
-- Purpose: Column-selected read of FND_FLEX_VALUES — auto-generated from field metadata
-- Grain : One row per FLEX_VALUE_ID
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.FLEX_VALUE_ID AS "Surrogate key of the flexfield value",
t.FLEX_VALUE_SET_ID AS "The value set this value belongs to — joins to FND_FLEX_VALUE_SETS",
t.FLEX_VALUE AS "The stored segment value itself",
t.ENABLED_FLAG AS "Whether the value is active",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date",
t.SUMMARY_FLAG AS "Whether this is a summary (rollup) value rather than a postable detail value",
t.PARENT_FLEX_VALUE_LOW AS "Parent value for dependent value sets — the independent value this row is valid under",
t.VALUE_CATEGORY AS "Descriptive-flexfield context category on the value",
t.STRUCTURED_HIERARCHY_LEVEL AS "Hierarchy level for structured value sets"
FROM <catalog>.<schema>.FND_FLEX_VALUES t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.FLEX_VALUE_ID = <FLEX_VALUE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.FLEX_VALUE_ID;4 parameters not filled: <catalog>, <schema>, <FLEX_VALUE_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON FND_FLEX_VALUES.FLEX_VALUE_SET_ID = FND_FLEX_VALUE_SETS.FLEX_VALUE_SET_ID