Search Results fnd_lookup_values

Overview

The FND_LOOKUP_VALUES table is a core repository for application-specific, user-maintained code values, historically known as QuickCodes, within the Oracle E-Business Suite (EBS) Application Object Library. It serves as the central data store for static lists of values (LOVs) used throughout the EBS application modules, enabling the configuration and localization of standardized codes such as statuses, types, categories, and priorities. Its role is fundamental to providing configurable, translatable, and secure reference data that drives application behavior and user interface consistency across the global enterprise.

Key Information Stored

The table's structure is designed to support multilingual, multi-organization data with security controls. The primary key uniquely identifies a lookup entry through a combination of LOOKUP_TYPE (the category, e.g., 'YES_NO'), LANGUAGE (the translation language code), LOOKUP_CODE (the stored value, e.g., 'Y'), SECURITY_GROUP_ID (for data partitioning in Multi-Org Access Control), and VIEW_APPLICATION_ID (the application owning the lookup type). Other critical columns include MEANING (the display value, e.g., 'Yes'), DESCRIPTION (a longer description), ENABLED_FLAG to control active status, START_DATE_ACTIVE and END_DATE_ACTIVE for date-range control, and DISPLAY_SEQUENCE for ordering in LOVs. The data is intrinsically linked to its parent definition table, FND_LOOKUP_TYPES.

Common Use Cases and Queries

This table is queried extensively for populating application LOVs, validating form entries, and generating reports. A standard pattern for retrieving active values for a specific lookup type, such as 'YES_NO', in a session's language is:

• SELECT lookup_code, meaning FROM fnd_lookup_values WHERE lookup_type = 'YES_NO' AND language = USERENV('LANG') AND enabled_flag = 'Y' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY display_sequence;

Common administrative tasks include auditing enabled values, identifying obsolete entries by checking for disabled flags or past end dates, and analyzing usage across modules by joining on LOOKUP_TYPE to FND_LOOKUP_TYPES. Reporting often involves translating codes to their user-friendly MEANING for clarity in output.

Related Objects

The primary related object is the parent definition table, FND_LOOKUP_TYPES, which defines the lookup categories via a foreign key relationship. As per the provided metadata, FND_LOOKUP_VALUES is referenced by several application tables, such as PA_DRAFT_INVOICE_ITEMS and JTF_OBJECT_MAPPINGS, which store foreign keys to specific lookup entries for classification. For programmatic access and data maintenance, developers typically use the public API FND_LOOKUP_VALUES_PKG rather than executing direct DML on the table, ensuring proper validation and business rule enforcement. The FND_FLEX_VALUES table serves a similar but distinct purpose for flexfield segment values.