Skip to content
EBS Reference

FND_LOOKUP_VALUES

Schema: APPLSYScontrolLanguage-striped

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)

Module: FoundationNot org-partitioned
Notes

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.
In field listings, K marks a primary-key field.

Fields

12 fields · 5 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1LOOKUP_TYPELookup type — the name of the code list this row belongs toVARCHAR2
Key
2LOOKUP_CODELookup code — the stored value coded columns carryVARCHAR2
Key
3LANGUAGELanguage of this row's meaning and description — filter to one or decode joins multiplyVARCHAR2
Key
4VIEW_APPLICATION_IDApplication scope of the lookup type — part of the full keyNUMBER
Key
5SECURITY_GROUP_IDSecurity group — part of the full key; 0 in most installsNUMBER
Key
6MEANINGThe short display label the code decodes toVARCHAR2
7DESCRIPTIONLonger description of the codeVARCHAR2
8SOURCE_LANGThe language this row's text was translated fromVARCHAR2
9ENABLED_FLAGWhether the code is activeVARCHAR2
10START_DATE_ACTIVEEffectivity start dateDATE
11END_DATE_ACTIVEEffectivity end dateDATE
12TAGFree-form grouping tag some lookup types use to sub-classify codesVARCHAR2

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.

Query parameters
-- ============================================================
-- 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

  • MTL_SYSTEM_ITEMS_BFND_LOOKUP_VALUESFND lookup decode · N:1
    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>'
  • OE_ORDER_HEADERS_ALLFND_LOOKUP_VALUESFND lookup decode · N:1
    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>'
  • OE_ORDER_LINES_ALLFND_LOOKUP_VALUESFND lookup decode · N:1
    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>'

Browse more Foundationtables →

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.