Results for “fnd_lookups”

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

Overview

FND_LOOKUPS is a view owned by the APPS schema within the FND — Application Object Library product. It presents Oracle Application Object Library QuickCodes, which are the extensible code/value pairs used throughout Oracle E-Business Suite to populate flexfield segments, list of values, validation sets, and application-specific enumerations. The view exposes the runtime-visible, language-appropriate subset of lookup values so that reports, concurrent programs, forms, and integrations can resolve a stored lookup code into its user-facing meaning without embedding hard-coded descriptions.

The view is central to EBS reporting and integration because QuickCodes are the canonical mechanism for lightweight reference data. Rather than joining directly to the underlying lookup value storage, consumers query FND_LOOKUPS to obtain only those rows that pass Oracle's language and security filters, which keeps reporting consistent with what the application itself presents to end users.

Underlying Base Objects

FND_LOOKUPS is defined over FND_LOOKUP_VALUES, referenced through a synonym, combined with logic from the FND_GLOBAL package. The view text filters and projects the base rows as follows:

• LANGUAGE = USERENV('LANG'), restricting output to the session's current language so that meanings and descriptions are returned in the appropriate locale.
• VIEW_APPLICATION_ID = 0, limiting the view to the shared, non-application-specific lookup set.
• SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LOOKUP_TYPE, VIEW_APPLICATION_ID), applying the lookup security group function from FND_GLOBAL to restrict rows according to the active security context.

Because the view delegates filtering to FND_GLOBAL and the FND_LOOKUP_VALUES synonym, it acts as a secured, language-aware projection rather than a physical table. Any change to base lookup values is immediately reflected through the view.

Key Columns

• LOOKUP_TYPE — the lookup category or code type, grouping related values (for example, a status or priority set).
• LOOKUP_CODE — the stored internal code value referenced by transactional and setup data.
• MEANING — the translated, user-facing label associated with the code in the session language.
• DESCRIPTION — extended descriptive text for the lookup value, also language-sensitive.
• ENABLED_FLAG — indicates whether the value is active (Y) or disabled (N) for entry and display.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range controlling when the value is valid.
• LEAF_NODE — flag used in hierarchical or dependent lookup structures to identify terminal nodes.

Common Use Cases and Queries

The most frequent scenario is resolving stored codes to meanings in a report or integration extract. For example, retrieving all enabled values for a given lookup type:

• SELECT lookup_code, meaning, description FROM fnd_lookups WHERE lookup_type = 'MY_LOOKUP_TYPE' AND enabled_flag = 'Y' ORDER BY lookup_code;
• Validating that an incoming interface value is a currently active QuickCode before loading it into a transaction table.
• Driving list-of-values and parameter pickers in custom concurrent programs and OAF or Forms extensions.
• Comparing configuration across environments by extracting lookup values for reference-data reconciliation.

Because the view enforces language and security filtering, queries against FND_LOOKUPS produce results aligned with the application's own presentation, reducing discrepancies between repository data and user-visible reference values.