FND_FLEX_VALUE_SETS
Schema: APPLSYScontrolValue set definitions for key and descriptive flexfields — one row per value set with its validation type, format rules, and size limits; the configuration that gives SEGMENTn columns their meaning
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
8 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | FLEX_VALUE_SET_ID | Surrogate key of the value set | NUMBER | Key |
| 2 | FLEX_VALUE_SET_NAME | The value set's unique name — how setup screens and practitioners refer to it | VARCHAR2 | |
| 3 | VALIDATION_TYPE | How values are validated — none, independent, dependent, table-validated, special, or pair | VARCHAR2 | |
| 4 | FORMAT_TYPE | Data format of the values (char, number, date…) | VARCHAR2 | |
| 5 | MAXIMUM_SIZE | Maximum length of a value in this set | NUMBER | |
| 6 | PARENT_FLEX_VALUE_SET_ID | For dependent value sets, the independent set this one depends on | NUMBER | |
| 7 | DESCRIPTION | Description of the value set | VARCHAR2 | |
| 8 | LONGLIST_FLAG | Whether the list is too long for a poplist — a UI hint, occasionally useful for sizing | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading FND_FLEX_VALUE_SETSon 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_VALUE_SETS — Value set definitions for key and descriptive flexfields — one row per value set with its validation type, format rules, and size limits; the configuration that gives SEGMENTn columns their meaning
-- Purpose: Column-selected read of FND_FLEX_VALUE_SETS — auto-generated from field metadata
-- Grain : One row per FLEX_VALUE_SET_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_SET_ID AS "Surrogate key of the value set",
t.FLEX_VALUE_SET_NAME AS "The value set's unique name — how setup screens and practitioners refer to it",
t.VALIDATION_TYPE AS "How values are validated — none, independent, dependent, table-validated, special, or pair",
t.FORMAT_TYPE AS "Data format of the values (char, number, date…)",
t.MAXIMUM_SIZE AS "Maximum length of a value in this set",
t.PARENT_FLEX_VALUE_SET_ID AS "For dependent value sets, the independent set this one depends on",
t.DESCRIPTION AS "Description of the value set",
t.LONGLIST_FLAG AS "Whether the list is too long for a poplist — a UI hint, occasionally useful for sizing"
FROM <catalog>.<schema>.FND_FLEX_VALUE_SETS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.FLEX_VALUE_SET_ID = <FLEX_VALUE_SET_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_SET_ID;4 parameters not filled: <catalog>, <schema>, <FLEX_VALUE_SET_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