Results for “fnd_lookup_values”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_LOOKUP_VALUES is the foundational QuickCode value table within Oracle E-Business Suite, owned by the APPLSYS schema and delivered by the FND — Application Object Library product. It stores the individual code values that populate every extensible and predefined lookup type used across the EBS application stack. Where FND_LOOKUP_TYPES defines the container (the named lookup, its description, and application context), FND_LOOKUP_VALUES holds the actual selectable entries — the "Yes/No" flags, status codes, reason codes, and other enumerated values that drive validation lists, flexfield segments, and form-level list of values throughout Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign-key structure classifies FND_LOOKUP_VALUES as hub-leaning. It behaves as a reference hub keyed by a composite business key, with descriptive and attribute columns acting as satellite-style payload. This classification should be treated as a modeling suggestion rather than a documented Oracle architectural statement. Because lookups are referenced pervasively, the table functions as a central reference point that many transactional and setup tables depend upon.

Key Information Stored

The most operationally significant columns are:

  • LOOKUP_TYPE — the code identifying which lookup (e.g. a status or reason lookup) a value belongs to; the primary join to FND_LOOKUP_TYPES.
  • LOOKUP_CODE — the stored, language-independent code value referenced by application data.
  • MEANING — the displayed, translatable description of the code shown to users.
  • DESCRIPTION — extended free-text context for the value.
  • LANGUAGE — the language for which this value and translation apply; supports multilingual installations.
  • ENABLED_FLAG — controls whether the value is active and selectable.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the value is valid.
  • VIEW_APPLICATION_ID — the application context under which the lookup value is viewed.
  • SECURITY_GROUP_ID — the security group (typically 0 in a standard EBS installation) with which the value is associated.
  • TERRITORY_CODE — optional territory qualification for the value.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-defined extensibility.
  • SOURCE_LANG and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — audit and translation-provenance metadata.

The primary key is FND_LOOKUP_VALUES_PK, a composite surrogate over LOOKUP_TYPE, LANGUAGE, LOOKUP_CODE, SECURITY_GROUP_ID, and VIEW_APPLICATION_ID. The documented business-key candidates are the unique indexes FND_LOOKUP_VALUES_U1 (LOOKUP_TYPE, VIEW_APPLICATION_ID, LOOKUP_CODE, SECURITY_GROUP_ID, LANGUAGE, ZD_EDITION_NAME) and FND_LOOKUP_VALUES_U2 (LOOKUP_TYPE, VIEW_APPLICATION_ID, MEANING, SECURITY_GROUP_ID, LANGUAGE, ZD_EDITION_NAME). In 12.2.2 the physical table carries 36 documented columns.

Common Use Cases and Queries

The table is queried whenever an application must validate or resolve a lookup code. A typical resolution joins values to their type to retrieve the display meaning:

  • Retrieve active values for a lookup: SELECT LOOKUP_CODE, MEANING FROM FND_LOOKUP_VALUES WHERE LOOKUP_TYPE = :type AND LANGUAGE = USERENV('LANG') AND ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
  • Confirm whether a code is valid in context: query by LOOKUP_TYPE, LOOKUP_CODE, and VIEW_APPLICATION_ID.
  • Reporting joins to FND_LOOKUP_TYPES to select the value's MEANING rather than storing decoded text.
  • Identifying unused or obsolete codes for cleanup or migration, and auditing DFF attribute usage across lookups.

Applications should treat lookups as read-only reference data and manipulate them through supported lookup maintenance forms or the FND_LOOKUPS API rather than direct DML.

Related Objects