Search Results product_attribute_context




Overview

APPS.QPFV_PRODUCT_EXCLUSIONS is a read-only Oracle E-Business Suite view that exposes the subset of pricing attribute records in which the excluder flag is set to "Y". It is a filtered projection of the QP_PRICING_ATTRIBUTES table, restricted to rows that define products to be excluded from a price list line. Because the view is defined with the WITH READ ONLY clause, it is intended for query and reporting purposes only; all maintenance of the underlying modification data must occur through the pricing engine or the Oracle Pricing forms.

In the ETRM 12.2.2 metadata, the view is owned by APPS and references QP_PRICE_LIST_LINE_UTIL and QP_QP_FORM_PRICING_ATTR as packages, plus QP_PRICING_ATTRIBUTES as a synonym. This places the view squarely within the Oracle Advanced Pricing (QP) module, where it supports the price list modification and product inclusion/exclusion framework used to qualify list lines.

Underlying Base Objects

The view is defined over QP_PRICING_ATTRIBUTES, which stores the attribute qualifiers and product exclusion records associated with pricing list lines. The predicate WHERE excluder_flag = 'Y' is the sole filter, so QPFV_PRODUCT_EXCLUSIONS surfaces only exclusionary rows, not inclusion rows or general qualifiers. Two PL/SQL packages are invoked in the SELECT list to resolve display values:

  • QP_QP_FORM_PRICING_ATTR.GET_ATTRIBUTE — returns the descriptive attribute name for the given product_attribute_context and product_attribute, translating stored identifiers into user-facing meanings.
  • QP_PRICE_LIST_LINE_UTIL.GET_PRODUCT_VALUE — returns the resolved product value for the combination of context, attribute, and product_attr_value, providing the display form of the excluded product.

Because these are packages rather than tables, each row retrieval performs function calls, which affects query performance and should be considered when writing large extracts.

Key Columns

Common Use Cases and Queries

QPFV_PRODUCT_EXCLUSIONS is typically used to audit which products have been excluded from specific list lines, to diagnose pricing qualification behavior, and to extract exclusion data for integration with external pricing or order capture systems. A basic query returns all exclusions for a given list line:

SELECT list_line_id,
       product_attribute_context,
       product_attribute,
       product_attr_value
FROM   apps.qpfv_product_exclusions
WHERE  list_line_id = :p_list_line_id;

To isolate exclusions defined under a particular context (the user's search term), filter on PRODUCT_ATTRIBUTE_CONTEXT:

SELECT list_line_id,
       product_attribute_context,
       product_attr_value
FROM   apps.qpfv_product_exclusions
WHERE  product_attribute_context = :p_context;

Because the view is read-only and resolves descriptive values through package functions, reports should select only the columns required and join to QP_PRICING_ATTRIBUTES or QP_LIST_LINES when additional list header detail is needed. Data modification must always be performed against the base pricing structures through supported Oracle Pricing functionality.