FND_LOOKUP_VALUES
Schema: APPLSYScontrolLanguage-stripedThe generic lookup table — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per language; the decode target for coded columns across every module (EBS's analog of JDE's UDC table)
Language-striped directly (no _B/_TL split): meanings repeat per installed language, with SOURCE_LANG marking the original — always filter LANGUAGE or decode joins multiply rows. The full key includes VIEW_APPLICATION_ID and SECURITY_GROUP_ID; most decodes can treat LOOKUP_TYPE + LOOKUP_CODE + LANGUAGE as the working key.
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
12 fields · 5 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LOOKUP_TYPE | Lookup type — the name of the code list this row belongs to | VARCHAR2 | Key |
| 2 | LOOKUP_CODE | Lookup code — the stored value coded columns carry | VARCHAR2 | Key |
| 3 | LANGUAGE | Language of this row's meaning and description — filter to one or decode joins multiply | VARCHAR2 | Key |
| 4 | VIEW_APPLICATION_ID | Application scope of the lookup type — part of the full key | NUMBER | Key |
| 5 | SECURITY_GROUP_ID | Security group — part of the full key; 0 in most installs | NUMBER | Key |
| 6 | MEANING | The short display label the code decodes to | VARCHAR2 | |
| 7 | DESCRIPTION | Longer description of the code | VARCHAR2 | |
| 8 | SOURCE_LANG | The language this row's text was translated from | VARCHAR2 | |
| 9 | ENABLED_FLAG | Whether the code is active | VARCHAR2 | |
| 10 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 11 | END_DATE_ACTIVE | Effectivity end date | DATE | |
| 12 | TAG | Free-form grouping tag some lookup types use to sub-classify codes | VARCHAR2 |
Field provenance: hand-curated. 5 key fields.
Boilerplate SQL
Starting point for reading FND_LOOKUP_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_LOOKUP_VALUES — The generic lookup table — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per language; the decode target for coded columns across every module (EBS's analog of JDE's UDC table)
-- Purpose: Column-selected read of FND_LOOKUP_VALUES — auto-generated from field metadata
-- Grain : One row per LOOKUP_TYPE + LOOKUP_CODE + VIEW_APPLICATION_ID + SECURITY_GROUP_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.LOOKUP_TYPE AS "Lookup type — the name of the code list this row belongs to",
t.LOOKUP_CODE AS "Lookup code — the stored value coded columns carry",
t.LANGUAGE AS "Language of this row's meaning and description — filter to one or decode joins multiply",
t.VIEW_APPLICATION_ID AS "Application scope of the lookup type — part of the full key",
t.SECURITY_GROUP_ID AS "Security group — part of the full key; 0 in most installs",
t.MEANING AS "The short display label the code decodes to",
t.DESCRIPTION AS "Longer description of the code",
t.SOURCE_LANG AS "The language this row's text was translated from",
t.ENABLED_FLAG AS "Whether the code is active",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date",
t.TAG AS "Free-form grouping tag some lookup types use to sub-classify codes"
FROM <catalog>.<schema>.FND_LOOKUP_VALUES t
WHERE
t.LANGUAGE = '<language>' -- one language or rows multiply; translations fall back to SOURCE_LANG
-- AND t.LOOKUP_TYPE = '<LOOKUP_TYPE>'
-- AND t.LOOKUP_CODE = '<LOOKUP_CODE>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.LOOKUP_TYPE;6 parameters not filled: <catalog>, <schema>, <language>, <LOOKUP_TYPE>, <LOOKUP_CODE>, <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 MTL_SYSTEM_ITEMS_B.ITEM_TYPE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'ITEM_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'ON OE_ORDER_HEADERS_ALL.FLOW_STATUS_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'FLOW_STATUS' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'ON OE_ORDER_LINES_ALL.FLOW_STATUS_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'LINE_FLOW_STATUS' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'