Search Results qp_lookups




Overview
Explore in AI Chat

Overview

QP_LOOKUPS is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Advanced Pricing (QP) product family and exposes Oracle Pricing lookup codes in a pre-filtered, security-aware form. Rather than querying the underlying Oracle Application Object Library (FND) lookup infrastructure directly, applications and reports can query QP_LOOKUPS to retrieve only those lookup values belonging to the Pricing application, with language and security-group filtering already applied by the view definition.

The view is documented as VALID and is treated as the canonical read interface for Pricing lookup values. Because Advanced Pricing relies on lookups to drive configurable behavior — pricing contexts, modifier attributes, adjustment reasons, qualifier groupings, and similar constructs — QP_LOOKUPS provides a convenient, denormalized window into the codes that govern much of the pricing engine's configuration. It is read-only by design and should never be used as a maintenance surface; lookup values are maintained through the Application Developer responsibility against FND_LOOKUP_VALUES.

Underlying Base Objects

The view is defined over a single documented base object: the FND_LOOKUP_VALUES synonym, which resolves in the APPS schema to the FND application object library table that stores all lookup value rows across the E-Business Suite. The view text applies three predicates against that synonym:

  • LANGUAGE = USERENV('LANG') — restricts rows to the language of the current session, returning the translated MEANING and DESCRIPTION appropriate to the user's environment.
  • VIEW_APPLICATION_ID = 661 — restricts rows to the Advanced Pricing (QP) application, application ID 661, ensuring only Pricing-owned lookup types are exposed.
  • SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(...) — invokes the standard FND security-group function, so the view respects the lookup security model configured for the environment.

Direct access to FND_LOOKUP_VALUES is generally discouraged in custom code because it exposes lookups across all applications and bypasses language and security filtering. QP_LOOKUPS encapsulates those rules, making it the preferred access path for Pricing-specific lookup data.

Key Columns

The view projects seven columns from FND_LOOKUP_VALUES. Each corresponds directly to a column of the same name on the base table:

  • LOOKUP_TYPE — the internal name of the lookup type, the grouping key for related codes (for example, a Pricing adjustment reason lookup).
  • LOOKUP_CODE — the stored code value used internally by Pricing logic; combined with LOOKUP_TYPE it forms the logical key.
  • MEANING — the user-facing, translatable label displayed in the application and typically the value shown in reports.
  • DESCRIPTION — an optional longer, translatable description of the code.
  • ENABLED_FLAG — indicates whether the code is currently active (Y) or disabled (N); disabled codes remain visible but are not selectable in the application.
  • START_DATE_ACTIVE — the date from which the code becomes valid; null implies no lower bound.
  • END_DATE_ACTIVE — the date after which the code is no longer valid; null implies no upper bound.

Because the view filters on language, the MEANING and DESCRIPTION values returned are already language-resolved, eliminating the need for callers to join translation tables themselves.

Common Use Cases and Queries

Typical scenarios include building reports or concurrent programs that need valid Pricing lookup values, validating user-entered codes, and populating LOV or integration payloads with active, in-date codes. A representative query retrieves all enabled, currently effective codes for a given lookup type:

  • SELECT lookup_code, meaning, description FROM qp_lookups WHERE lookup_type = :p_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
  • SELECT DISTINCT lookup_type FROM qp_lookups ORDER BY lookup_type; — enumerates the Pricing lookup types available.

For consistent formatting, always filter or convert MEANING with the appropriate character semantics. When diagnosing date-range anomalies, compare START_DATE_ACTIVE and END_DATE_ACTIVE against the current date rather than relying on ENABLED_FLAG alone.