Search Results qp_price_lists_v




Overview
Explore in AI Chat

Overview

QP_PRICE_LISTS_V is an APPS-owned view in the Oracle E-Business Suite Advanced Pricing (QP) module. Its documented purpose is to expose "Price List information" and it is explicitly "Provided for backward compatibility for other applications." This statement is significant: the view predates the current pricing data model, in which price lists and agreements are stored as list headers using a list type discriminator. Rather than representing a first-class integration interface, QP_PRICE_LISTS_V exists so that legacy code, forms, reports, and third-party integrations written against an earlier price list API continue to function after the introduction of the QP_LIST_HEADERS family of objects.

Accordingly, the view should be treated as a compatibility shim. New development should generally target QP_LIST_HEADERS_VL and the associated pricing public APIs, while existing consumers can continue to read QP_PRICE_LISTS_V without modification. In reported EBS versions 12.1.1 and 12.2.2, the view carries a VALID status in the APPS schema.

Underlying Base Objects

The documented view text is:

SELECT ROW_ID, LIST_HEADER_ID, ... QP_PRICE_LIST_PVT.GET_SECONDARY_PRICE_LIST(LIST_HEADER_ID), ... FROM QP_LIST_HEADERS_VL WHERE LIST_TYPE_CODE IN ('PRL', 'AGR')

Two base objects are referenced:

  • QP_LIST_HEADERS_VL (VIEW) — the current, translated list header view. QP_PRICE_LISTS_V selects from it and filters on LIST_TYPE_CODE IN ('PRL', 'AGR'), meaning it returns only price lists (PRL) and agreements (AGR). Other list types, such as modifiers or promotion lists, are excluded.
  • QP_PRICE_LIST_PVT (PACKAGE) — a PL/SQL package whose function GET_SECONDARY_PRICE_LIST(LIST_HEADER_ID) is invoked inline in the SELECT list. This is a scalar function call executed per row, used to derive the secondary price list identifier.

Because the ROW_ID column is selected but not aliased, and the function column is anonymous, the view presents a mix of directly projected columns and a computed column. Note that the column list assigns the name PRICE_LIST_ID where the view text selects LIST_HEADER_ID; the exposed column name therefore differs from the underlying column name.

Key Columns

The view exposes standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID), and fifteen descriptive flexfield columns (CONTEXT, ATTRIBUTE1 through ATTRIBUTE15). Functional columns include:

  • PRICE_LIST_ID — the list header identifier (sourced from LIST_HEADER_ID); the primary reference for a price list or agreement.
  • ROW_ID — a row identifier column carried forward for compatibility.
  • NAME — the price list or agreement name from the translated header view.
  • CURRENCY_CODE — the currency in which list prices are expressed.
  • ROUNDING_FACTOR — the rounding rule applied to computed prices.
  • SECONDARY_PRICE_LIST_ID — the value returned by QP_PRICE_LIST_PVT.GET_SECONDARY_PRICE_LIST, identifying a related price list used in multi-currency or secondary pricing scenarios.
  • SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, TERMS_ID — shipping, freight, and payment terms associated with the list.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date range of the list.
  • COMMENTS, DESCRIPTION — free-text descriptive attributes.

Common Use Cases and Queries

Typical uses include listing active price lists for a currency, joining list headers to list lines for reporting, and validating legacy integrations that still reference the view. A representative query follows.

SELECT price_list_id, name, currency_code, rounding_factor, start_date_active, end_date_active FROM apps.qp_price_lists_v WHERE currency_code = 'USD' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

For pricing data, avoid selecting the full attribute set unless the flexfield context is required, and always qualify the view with the APPS schema and apply the appropriate operating unit or security predicates used by the calling application. Where possible, migrate new logic to QP_LIST_HEADERS_VL and the QP public APIs to remain supported.