Search Results qpbv_products




Overview
Explore in AI Chat

Overview

QPBV_PRODUCTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Oracle Advanced Pricing (QP) module. Its purpose is to expose information about a "Buy" product associated with either a modifier or a price list line. In practice, the view presents the pricing attribute rows that identify the product, its attribute context, its value, and its associated unit of measure, filtered so that only non-excluded pricing attributes are returned.

Because QP pricing structures store product information as attribute/value pairs rather than as direct foreign keys to inventory items, QPBV_PRODUCTS provides a flattened, query-friendly projection over those pairs. This makes it useful for reporting, data extraction, and integration scenarios where a developer or analyst needs to resolve which product a given price list line or modifier applies to, together with the product's unit of measure. The view is documented as VALID and is referenced in ETRM metadata for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object, the synonym QP_PRICING_ATTRIBUTES, which resolves to the underlying Advanced Pricing attribute table in the APPS schema. The view text selects ten columns from this source and applies two restrictive predicates:

  • EXCLUDER_FLAG = 'N' — only rows that are not flagged as excluders are returned, ensuring the view reflects active, includable pricing attributes rather than exclusion rules.
  • PRICING_ATTRIBUTE_CONTEXT IS NULL OR PRICING_ATTRIBUTE_CONTEXT = 'VOLUME' — restricts results to rows with no pricing attribute context or to those in the VOLUME context, aligning with the "Buy" product orientation of the view.

No joins, aggregations, or outer queries are present in the view definition. Consequently, QPBV_PRODUCTS inherits the row-level granularity of QP_PRICING_ATTRIBUTES and does not itself consolidate multiple attribute rows into a single product record. The PRODUCT_ATTRIBUTE_CONTEXT column is exposed from the base table but is not the same column referenced in the WHERE clause's PRICING_ATTRIBUTE_CONTEXT predicate.

Key Columns

  • PRODUCT_ATTRIBUTE_CONTEXT — the context under which the product attribute is defined; distinguishes the type or category of attribute being described.
  • PRODUCT_ATTRIBUTE — the name of the product attribute, i.e., the dimension used to identify the product (for example, an inventory item identifier or a product classification attribute).
  • PRODUCT_ATTR_VALUE — the value assigned to that attribute, representing the actual product reference on the pricing line.
  • PRODUCT_UOM_CODE — the unit of measure code associated with the product. This is the column commonly retrieved when users search for "product_uom_code" in the context of Advanced Pricing product data.
  • LIST_LINE_ID — identifier of the price list line (or modifier line) to which the product attribute belongs.
  • LIST_HEADER_ID — identifier of the parent price list header, enabling grouping of lines by list.
  • CREATION_DATE, CREATED_BY — standard audit columns recording when and by whom the row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns recording the most recent change.

Common Use Cases and Queries

Typical scenarios include resolving the product and UOM behind a price list line for reporting, verifying that a modifier's buy product is correctly configured, and extracting product/UOM combinations for downstream integration. A basic query to retrieve products and their units of measure for a given price list is:

  • SELECT list_header_id, list_line_id, product_attribute, product_attr_value, product_uom_code FROM qpbv_products WHERE list_header_id = :p_list_header_id;
  • SELECT product_attr_value, product_uom_code FROM qpbv_products WHERE list_line_id = :p_list_line_id;
  • SELECT DISTINCT product_uom_code FROM qpbv_products ORDER BY product_uom_code;

Because the view applies the EXCLUDER_FLAG and context filters internally, queries against it automatically omit exclusion rows and non-qualifying attribute contexts, simplifying the SQL required by report authors and integration developers.