Search Results qp_list_lines_v




Overview
Explore in AI Chat

Overview

QP_LIST_LINES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Advanced Pricing (QP). It exposes price list line information and is the primary data source for the List Lines block in the Price Lists form. In Release 12.1.1 and 12.2.2 the view presents a denormalized picture of list line records joined to their associated pricing attributes, allowing a single query to retrieve both the pricing definition (for example list price, percent price, formula, and price break details) and the product or pricing attribute values that qualify that line.

Because the view carries descriptive columns rather than raw foreign keys alone, it is well suited to reporting, data extraction, and integration interfaces that need human-readable price list content. Technically it is a view over QP_LIST_LINES and QP_PRICING_ATTRIBUTES, with a synonym reference to QP_PRICE_LIST_LINE_UTIL, which supplies the price list header context that the form requires.

Underlying Base Objects

The documented referenced base objects are QP_LIST_LINES (accessed through a synonym), QP_PRICING_ATTRIBUTES (also through a synonym), and the QP_PRICE_LIST_LINE_UTIL package. The view text confirms that QPLL is QP_LIST_LINES and QPPR is QP_PRICING_ATTRIBUTES. QPPR supplies the pricing attribute context, attribute name, and value columns that appear in the view's output.

The package QP_PRICE_LIST_LINE_UTIL is referenced in the definition to derive the price list header identifier (PA_LIST_HEADER_ID) required by the Price Lists form. This join through a PL/SQL package means the view is tuned for the form's List Lines block rather than as a general-purpose relational join, and queries against it should expect the pricing attribute row to be the qualifying row for the list line.

Key Columns

Common Use Cases and Queries

Typical uses include price list reporting, verifying price line setup before order entry, and extracting list line content for downstream pricing engines or data warehouses. Because the view is form-oriented, single-line lookups by LIST_LINE_ID are fast, while broad extracts may perform better against QP_LIST_LINES directly.

Example: retrieve active list lines for a specific price list and item.

SELECT list_line_id, list_header_id, list_line_no,
       inventory_item_id, list_price, percent_price,
       start_date_active, end_date_active, list_line_type_code
FROM   apps.qp_list_lines_v
WHERE  list_header_id = :p_list_header_id
AND    inventory_item_id = :p_item_id
AND    TRUNC(SYSDATE) BETWEEN TRUNC(start_date_active) AND TRUNC(NVL(end_date_active, SYSDATE + 3650))
ORDER BY list_line_no;

Example: list pricing attributes associated with price list lines for a header.

SELECT list_line_id,
       pricing_attribute_context,
       pricing_attribute,
       pricing_attr_value_from,
       pricing_attr_value
FROM   apps.qp_list_lines_v
WHERE  list_header_id = :p_list_header_id
ORDER BY list_line_id, pricing_attribute;

When joining to QP_LIST_HEADERS for descriptive context, use LIST_HEADER_ID on the view rather than PA_LIST_HEADER_ID, since the latter is intended for the form's internal navigation.