Results for “fnd_lookup_values_u1”

28 results




Overview
Explore in AI Chat

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

Overview

APPLSYS.FND_LOOKUP_VALUES is the Oracle Application Object Library repository for QuickCode lookup values in Oracle E-Business Suite 12.1.1 and 12.2.2. Every row defines one QuickCode within a lookup type, capturing its meaning, description, active date range, and language-specific text. Oracle Application Object Library reads this table to populate list of values (LOVs) for Application Object Library forms and for forms across all other EBS products, making it one of the most widely referenced seed data tables in the applications schema.

The table resides in the APPS_TS_SEED tablespace with PCTFREE 10, reflecting its role as seeded reference data rather than transactional data. Rows are keyed by LOOKUP_TYPE, LANGUAGE, LOOKUP_CODE, SECURITY_GROUP_ID, and VIEW_APPLICATION_ID. Because one row exists per QuickCode per installed language, multilingual sites maintain multiple rows for the same logical code. The FND design data reference is FND.FND_LOOKUP_VALUES.

From a dimensional modeling perspective, the mined relationship structure classifies this object as hub-leaning. This is a heuristic suggestion: LOOKUP_TYPE, LANGUAGE, and LOOKUP_CODE behave as stable business keys, while descriptive attributes such as MEANING, DESCRIPTION, and the ATTRIBUTE1–15 columns behave as satellite-style payload. Practitioners designing a warehouse layer may treat it as a hub with an attached descriptive satellite.

Key Information Stored

The columns below are the most operationally significant:

  • LOOKUP_TYPE (VARCHAR2 30) — the QuickCode lookup type; a foreign key to FND_LOOKUP_TYPES.
  • LOOKUP_CODE (VARCHAR2 30) — the QuickCode value itself, such as an internal code stored on transactions.
  • MEANING (VARCHAR2 80) — the user-facing display text for the code, surfaced in LOVs and reports.
  • DESCRIPTION (VARCHAR2 240) — supplementary explanatory text.
  • LANGUAGE (VARCHAR2 30) — the language of the row; drives translated LOV display.
  • SOURCE_LANG — the language whose text is mirrored when a translation is not yet supplied; edits to the source-language row propagate to untranslated rows.
  • ENABLED_FLAG — indicates whether the QuickCode is currently valid.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the date window during which the code is active; null end dates denote open-ended validity.
  • SECURITY_GROUP_ID and VIEW_APPLICATION_ID — organizational and application scoping attributes.
  • ZD_EDITION_NAME — editioning support used in the 12.2 online patching architecture.
  • Standard Who columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage.

The physical primary key is FND_LOOKUP_VALUES_PK (LOOKUP_TYPE, LANGUAGE, LOOKUP_CODE, SECURITY_GROUP_ID, VIEW_APPLICATION_ID). Two unique indexes act as business-key candidates: 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). Because the table is keyed on business columns rather than a generated surrogate, U1 is effectively the enforced uniqueness constraint for the logical QuickCode identity.

Common Use Cases and Queries

Typical scenarios include retrieving the display meaning for a stored code, validating that a code is active on a given date, and reporting on all values for a lookup type. A standard lookup of a code's meaning restricts by language and validity:

  • SELECT meaning FROM fnd_lookup_values WHERE lookup_type = :p_type AND lookup_code = :p_code AND language = USERENV('LANG') AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
  • Reporting all values for a type: SELECT lookup_code, meaning, enabled_flag, start_date_active, end_date_active FROM fnd_lookup_values WHERE lookup_type = :p_type ORDER BY lookup_code;
  • Detecting untranslated rows: SELECT lookup_code FROM fnd_lookup_values WHERE lookup_type = :p_type AND language = 'US' AND source_lang <> language;

Joined to FND_LOOKUP_TYPES, queries can filter to user-accessible types and exclude system-only types, which is the usual pattern for building custom LOVs. Because the table is seeded, custom lookup values should be inserted through supported means rather than direct DML.

Related Objects

  • APPLSYS.FND_LOOKUP_TYPES — parent of LOOKUP_TYPE; defines the type's name, description, and application context.
  • PA_DRAFT_INVOICE_ITEMS — references lookup values through FLE_LOOKUP_TYPE, FLE_LOOKUP_TYPE2, and FLE_LOOKUP_TYPE3, used for multiple flexfield-driven code references on draft invoice lines.
  • JTF_OBJECT_MAPPINGS — references lookup values via FLE_LOOKUP_TYPE for object-to-code mapping.
  • FND_LOOKUP_VALUES_U1 / U2 — the supporting unique indexes that enforce QuickCode and meaning uniqueness per language and application view.

These dependencies confirm FND_LOOKUP_VALUES as a reference hub serving downstream transactional and mapping tables across EBS modules.