Search Results pv_lookups




Overview
Explore in AI Chat

Overview

PV_LOOKUPS is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). It resides in the PV (Partner Management) product family and presents the set of Oracle Application Object Library lookup values that belong specifically to the Partner Management application. Rather than exposing every lookup code registered in the E-Business Suite, the view restricts its result set to lookup types owned by PV, identified by APPLICATION_ID = 691.

The view is read-only and is intended for inquiry, reporting, and integration purposes. It allows developers, concurrent programs, and external interfaces to resolve lookup codes into their translated meanings without querying the underlying FND tables directly. Because it enforces the session language and a fixed security group, consumers receive a deterministic, language-aware perspective of PV lookup configuration data.

Underlying Base Objects

The view is defined over two dictionary objects, referenced through synonyms in the APPS schema:

  • FND_LOOKUP_TYPES — supplies the lookup type definition and, critically, the APPLICATION_ID used to filter the rows to Partner Management.
  • FND_LOOKUP_VALUES — supplies the individual lookup codes, their meanings, descriptions, date ranges, enabled flags, and descriptive flexfield attributes.

The join logic applies three constraints. First, LV.LANGUAGE must equal USERENV('LANG'), which returns the language of the current session. Second, LV.LOOKUP_TYPE must equal LT.LOOKUP_TYPE, linking each value to its parent type. Third, LT.APPLICATION_ID must equal 691 (Partner Management), and LV.SECURITY_GROUP_ID must equal 0. The result is a sealed subset of the lookup repository relevant only to PV.

Key Columns

The view exposes the complete column list of FND_LOOKUP_VALUES. The most commonly used columns include:

  • LOOKUP_TYPE — the lookup type name, such as a partner-related classification code.
  • LOOKUP_CODE — the stored code value used in transactional tables.
  • MEANING — the user-facing, language-translated description of the code.
  • DESCRIPTION — supplementary text for the code.
  • ENABLED_FLAG — indicates whether the code is currently active (Y/N).
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the code is valid.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments that capture additional, customer-defined attributes.
  • TAG — a free-form tag value maintained against the lookup.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to decouple reporting logic from the FND base tables, to filter PV-specific lookups, and to join lookup meanings to transactional data. Because it is language-aware, it is also suited to multi-language environments.

A basic query listing active Partner Management lookup values:

  • SELECT lookup_type, lookup_code, meaning FROM pv_lookups WHERE enabled_flag = 'Y' ORDER BY lookup_type, lookup_code;

Retrieving values for a single lookup type within its effective window:

  • SELECT lookup_code, meaning, description FROM pv_lookups WHERE lookup_type = :p_lookup_type AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Joining lookup meanings to a transactional table:

  • SELECT t.code_column, l.meaning FROM some_pv_table t, pv_lookups l WHERE t.code_column = l.lookup_code AND l.lookup_type = :p_type;

Because the view filters on APPLICATION_ID = 691, it cannot return non-PV lookups; consumers requiring cross-application lookups must query FND_LOOKUP_VALUES directly. As with all APPS views, access should be granted through the appropriate responsibility and the view should be treated as read-only reference data.