Results for “qpbv_pricing_attributes”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The QPBV_PRICING_ATTRIBUTES view is a database object owned by the APPS schema within the Oracle E-Business Suite Advanced Pricing (QP) module. It exposes information about pricing attributes that are attached to either a modifier or a price list. In Oracle EBS 12.1.1 and 12.2.2, pricing attributes form the qualification and qualifying criteria layers that determine how price lists and modifiers are selected and applied during pricing engine evaluation. The view presents a filtered, consumer-friendly projection of the underlying pricing attribute data, restricting the result set to records where the pricing attribute context is populated and the excluder flag is not set. Because it resides in the APPS schema, it is accessible to reporting tools, concurrent programs, and integration interfaces that connect with the APPS credentials. The view is registered in ETRM as VALID, indicating that its definition compiles cleanly against the referenced base object.

Underlying Base Objects

The view is defined over a single documented base object: the synonym QP_PRICING_ATTRIBUTES, which resolves to the QP base table of the same name. The view text aliases this object as PA and projects a defined column list rather than using a wildcard. Two filter predicates are hard-coded into the definition: PRICING_ATTRIBUTE_CONTEXT IS NOT NULL and EXCLUDER_FLAG = 'N'. This means exclusion-type attribute rows and rows lacking a pricing attribute context are silently removed before any consumer query executes. Users cannot bypass these predicates, so the view is best understood as a "qualifying pricing attributes only" read layer rather than a full mirror of the base table.

Key Columns

• QUALIFICATION_IND — Indicates the qualification role of the attribute row. This column is central to the user's search and distinguishes how the attribute participates in modifier or price list qualification logic.
• LIST_HEADER_ID — Identifies the price list header to which the attribute belongs.
• LIST_LINE_ID — Identifies the specific price list line associated with the attribute.
• PRICING_PHASE_ID — Links the attribute to a pricing phase, relevant for modifier phase sequencing.
• PRICING_ATTRIBUTE_CONTEXT / PRICING_ATTRIBUTE / PRICING_ATTR_VALUE_FROM / PRICING_ATTR_VALUE_TO — Define the qualifying attribute, its context, and the value or range evaluated by the pricing engine.
• PRODUCT_ATTRIBUTE_CONTEXT / PRODUCT_ATTRIBUTE / PRODUCT_ATTR_VALUE / PRODUCT_UOM_CODE — Describe the product-side attribute used in qualification, including unit of measure.
• COMPARISON_OPERATOR_CODE — The operator applied when comparing the pricing attribute value against the qualifying value.
• EXCLUDER_FLAG — Always 'N' in this view due to the filter; exposes the underlying column for completeness.
• PRICING_ATTRIBUTE_ID — Primary identifier of the pricing attribute record.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include troubleshooting why a modifier or price list qualifies (or fails to qualify) for a given order line, reporting on the attribute criteria configured against price lists, and feeding qualification data into integration or analytics layers. The most common requirement involving the searched term is isolating qualification rows.

To retrieve qualification attributes for a specific price list:

SELECT list_header_id, list_line_id, pricing_attribute_context,
       pricing_attribute, pricing_attr_value_from, pricing_attr_value_to,
       comparison_operator_code, qualification_ind
FROM   apps.qpbv_pricing_attributes
WHERE  list_header_id = :p_list_header_id
AND    qualification_ind = 'Y';

To locate all rows tied to a modifier phase, filter on PRICING_PHASE_ID, and to profile value ranges, aggregate on COMPARISON_OPERATOR_CODE. Because the view already excludes non-qualifying context rows and excluder records, queries are generally simpler and less error-prone than against QP_PRICING_ATTRIBUTES directly, though consumers requiring exclusion rows must query the base table instead.