Skip to content
EBS Reference

FND_FLEX_VALUES

Schema: APPLSYScontrol

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

Identity
Module: FoundationNot org-partitioned
Notes

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
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

10 fields · 1 key

10 fields.

Table fields: position, field name, description, data type, and flags. 10 fields.
#FieldDescriptionTypeFlags
1FLEX_VALUE_IDSurrogate key of the flexfield valueNUMBER
Primary-key field
2FLEX_VALUE_SET_IDThe value set this value belongs to — joins to FND_FLEX_VALUE_SETSNUMBER
3FLEX_VALUEThe stored segment value itselfVARCHAR2
4ENABLED_FLAGWhether the value is activeVARCHAR2
5START_DATE_ACTIVEEffectivity start dateDATE
6END_DATE_ACTIVEEffectivity end dateDATE
7SUMMARY_FLAGWhether this is a summary (rollup) value rather than a postable detail valueVARCHAR2
8PARENT_FLEX_VALUE_LOWParent value for dependent value sets — the independent value this row is valid underVARCHAR2
9VALUE_CATEGORYDescriptive-flexfield context category on the valueVARCHAR2
10STRUCTURED_HIERARCHY_LEVELHierarchy level for structured value setsNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading FND_FLEX_VALUES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <FLEX_VALUE_ID>, <watermark>

-- ============================================================
-- 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;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • FND_FLEX_VALUESFND_FLEX_VALUE_SETSforeign key · N:1
    ON FND_FLEX_VALUES.FLEX_VALUE_SET_ID = FND_FLEX_VALUE_SETS.FLEX_VALUE_SET_ID

Browse more Foundation tables

More Foundation tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.