Search Results excluder_flag




Overview
Explore in AI Chat

Overview

QPBV_PRODUCT_EXCLUSIONS is an APPS-owned database view in the Oracle E-Business Suite Advanced Pricing (QP) module. It presents the subset of pricing attribute rows that act as product exclusions on a price list. In Oracle Advanced Pricing, a price list line can be qualified by product attributes (for example item, item category, or user-defined attributes). When such a line is instead used to exclude a product or product group from a pricing rule, the pricing attribute record is marked as an excluder. QPBV_PRODUCT_EXCLUSIONS exposes precisely those rows.

The view is defined as a filtered projection over QP_PRICING_ATTRIBUTES, returning only records where EXCLUDER_FLAG equals 'Y'. By exposing a pre-filtered result set, it serves as a convenience layer for reporting, integration, and custom code that needs to isolate exclusion-type product qualifiers without repeatedly coding the EXCLUDER_FLAG predicate. The naming convention—QPBV prefix—identifies it as a QP module view (QPBV = QP Base View), and its column list mirrors the underlying table, preserving identifiers, audit columns, and original system reference columns used for integrations.

Underlying Base Objects

The view is defined over a single referenced base object: QP_PRICING_ATTRIBUTES, accessed through a SYNONYM in the APPS schema. QP_PRICING_ATTRIBUTES is the core Advanced Pricing table that stores pricing attribute qualifiers associated with price list lines and pricing rules. Each row links a pricing attribute value to a list line or list header through identifiers such as LIST_LINE_ID, LIST_HEADER_ID, and PRICING_ATTRIBUTE_ID.

Because the view is a simple one-table projection with a WHERE clause, it is updatable in the sense that it inherits the base table's structure, but Oracle treats views with filtering predicates as logically restricted. DML against exclusion rows should generally be performed directly against QP_PRICING_ATTRIBUTES to avoid ambiguity. The view contains no joins or aggregations, so query performance mirrors that of the base table, subject to the EXCLUDER_FLAG filter.

Key Columns

  • LIST_LINE_ID — Identifier of the price list line to which the pricing attribute (and thus the exclusion) is attached.
  • EXCLUDER_FLAG — Flag indicating the record is an exclusion. Always 'Y' in this view by definition.
  • PRODUCT_ATTRIBUTE_CONTEXT — The context under which the product attribute is defined (for example, Item or a user-defined context).
  • PRODUCT_ATTRIBUTE — The specific product attribute being qualified, such as ITEM or CATEGORY.
  • PRODUCT_ATTR_VALUE — The value of the product attribute, i.e., the product, category, or attribute value being excluded.
  • LIST_HEADER_ID — Identifier of the parent price list header.
  • PRICING_ATTRIBUTE_ID — Primary key of the underlying pricing attribute record.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording who created and last modified the row and when.
  • ORIG_SYS_HEADER_REF, ORIG_SYS_LINE_REF, ORIG_SYS_PRICING_ATTR_REF — Original system references used to trace records back to source systems during integration.

Common Use Cases and Queries

Typical uses include auditing which products are excluded from a price list, diagnosing pricing discrepancies where an expected product does not receive a discount or promotion, and feeding exclusion data into integration or data-warehouse extracts. The view is also useful when validating pricing setup prior to order entry testing.

Example: list all product exclusions for a given price list header.

  • SELECT list_line_id, product_attribute, product_attr_value FROM qpbv_product_exclusions WHERE list_header_id = :header_id;

Example: identify all excluded items across active price lists.

  • SELECT list_header_id, list_line_id, product_attr_value FROM qpbv_product_exclusions WHERE product_attribute = 'ITEM';

Example: join exclusions to the price list header for reporting.

  • SELECT h.name, e.product_attribute, e.product_attr_value FROM qp_list_headers_vl h, qpbv_product_exclusions e WHERE h.list_header_id = e.list_header_id;

Because the EXCLUDER_FLAG predicate is already applied, queries against this view remain concise and self-documenting, reducing the risk of omitting the exclusion filter in custom reporting.