Results for “price_differential_dsp”

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

Overview

PO_PRICE_DIFF_LOOKUPS_V is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. It exposes the set of price differential lookup values that Purchasing makes available to end users when negotiating or defining supplier agreements, blanket purchase agreements, contracts, and standard purchase orders. In EBS terms, a price differential represents the mechanism by which a buyer specifies a percentage or amount added to or subtracted from a base price to arrive at a negotiated price. The view is a filtered, user-facing projection over the Oracle Application Object Library (FND) lookup infrastructure rather than a table that stores transactional purchasing data. Because it is a view, it carries no data of its own; it is a derived query and therefore remains VALID as long as the underlying FND lookup objects and the FND_GLOBAL package remain present and compiled in the database. Its principal role is to provide a controlled list of selectable price differential codes for Purchasing forms, concurrent programs, and reporting or integration layers that need to present or validate the same domain of values.

Underlying Base Objects

The documented metadata identifies three referenced base objects: FND_LOOKUP_TYPES_VL, FND_LOOKUP_VALUES_VL, and the FND_GLOBAL package. The view is defined as a join between the lookup type and lookup value views on both LOOKUP_TYPE and SECURITY_GROUP_ID. The lookup type view is restricted to LOOKUP_TYPE = 'PRICE DIFFERENTIALS' and APPLICATION_ID = 201, which is the Oracle Purchasing application identifier. The join further constrains VIEW_APPLICATION_ID to 0 on the lookup type and matches VIEW_APPLICATION_ID between the two source views. FND_GLOBAL is invoked through the function FND_GLOBAL.LOOKUP_SECURITY_GROUP, which enforces row-level lookup security so that only values visible to the current security group are returned. The net effect is that the view is a security-aware, application-scoped slice of the generic FND lookup framework.

Key Columns

• PRICE_DIFFERENTIAL_TYPE — the lookup code identifying the differential type, corresponding to LOOKUP_CODE in the underlying lookup values.
• PRICE_DIFFERENTIAL_DSP — the display meaning shown to users, derived from MEANING.
• PRICE_DIFFERENTIAL_DESC — the descriptive text, derived from DESCRIPTION.

The view text selects LOOKUP_CODE, MEANING, and DESCRIPTION and applies several filters: ENABLED_FLAG must be 'Y' (defaulting to 'Y' when null), the current SYSDATE must fall within the active date range (with defaulted start and end dates), and the codes 'STANDARD' and 'FIXED PRICE' are explicitly excluded, leaving only the genuine differential types.

Common Use Cases and Queries

Typical uses include populating a list of values in custom Purchasing extensions, validating a price differential entered through an interface or API, and driving reports that summarize negotiated pricing terms. A representative query is:

• SELECT price_differential_type, price_differential_dsp, price_differential_desc FROM apps.po_price_diff_lookups_v ORDER BY price_differential_dsp;
• SELECT price_differential_dsp FROM apps.po_price_diff_lookups_v WHERE price_differential_type = :p_type;

Because the view already enforces enablement, date activity, and lookup security, consumers do not need to replicate those predicates. This makes it suitable as a single source of truth for the Purchasing price differential domain across both 12.1.1 and 12.2.2 environments, where the FND lookup framework behaves consistently.