Search Results oe_lookups

Overview

OE_LOOKUPS is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the Order Management (ONT) product module. Its purpose is to expose the set of Oracle "QuickCodes" (lookups) that are specific to Order Management functionality, presenting them in a denormalized, query-friendly form. Rather than forcing report authors and interface developers to filter the much larger FND_LOOKUP_VALUES table by application, the view pre-applies the Order Management application context, returning only the lookup values that ONT relies upon for its configurable lists, statuses, and coded attributes.

In EBS 12.1.1 and 12.2.2 the object is documented as VALID and carries the description "Order Management QuickCodes values." Because it is a view rather than a base table, it introduces no storage of its own; it is a lightweight, read-only projection that inherits its data directly from the underlying Flexfields lookup infrastructure. This makes it a standard reference point for concurrent programs, BI Publisher data templates, OAF-based extensions, and inbound/outbound interface logic that must translate between stored lookup codes and their user-facing meanings.

Underlying Base Objects

The view is defined exclusively over FND_LOOKUP_VALUES, which is exposed in the APPS schema as a synonym. The defining query selects LOOKUP_TYPE, LOOKUP_CODE, MEANING, DESCRIPTION, ENABLED_FLAG, START_DATE_ACTIVE and END_DATE_ACTIVE from that base object, applying three restrictive predicates:

• LANGUAGE = USERENV('LANG') — restricts rows to the session's current language, ensuring user-facing MEANING text is returned in the appropriate installed language.
• VIEW_APPLICATION_ID = 660 — the application identifier for Order Management, which is the mechanism by which the view isolates ONT QuickCodes from all other applications' lookups.
• SECURITY_GROUP_ID = 0 — limits results to the standard (non-seeded-security-group) lookup records.

Consequently, OE_LOOKUPS has a strict one-to-many relationship with FND_LOOKUP_VALUES: a single lookup type in the view corresponds to multiple lookup code rows, and each row surfaced by the view maps to exactly one underlying FND_LOOKUP_VALUES record. No other base tables or joins are documented.

Key Columns

• LOOKUP_TYPE — the lookup category (for example, order or line-related code sets). Serves as the primary grouping key.
• LOOKUP_CODE — the stored, language-independent code value used internally by Order Management. This is the value persisted on transactional records.
• MEANING — the translatable, user-facing display value associated with the code.
• DESCRIPTION — optional supplemental descriptive text for the lookup value.
• ENABLED_FLAG — indicates whether the lookup value is currently active and available for selection.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling when the lookup value is valid.

Common Use Cases and Queries

Typical uses include decoding stored codes into display meanings within reports, validating interface input against valid ONT lookups, and populating selection lists in custom forms or pages. A representative query retrieving all active values for a given lookup type is:

SELECT lookup_code, meaning, description
FROM oe_lookups
WHERE lookup_type = :p_lookup_type
AND enabled_flag = 'Y'
AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view already filters by language and application, no additional FND application predicate is required in consuming code. Note that the search term "Olympia Restaurant Qr Code" is unrelated to this database object and does not correspond to any documented element of OE_LOOKUPS.