Results for “qp_attr_defns_pricing”

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

Overview

APPS.QPFV_ADDITIONAL_BUY_PRODUCTS is a read-only reporting view in the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite, exposed under the APPS schema. It presents the qualifier-side product and pricing attribute context associated with related modifiers, specifically those modifier relationships whose group type is constrained to 'QUALIFIER'. In pricing terms, a qualifier determines the eligibility conditions under which a modifier (a price adjustment such as a discount, surcharge, or promotion) becomes applicable. The view therefore surfaces the "additional buy product" attributes that must be satisfied for a related modifier to fire.

Its role is primarily reporting, diagnostic, and integration-oriented. Rather than maintaining denormalized attribute data of its own, the view assembles a business-friendly projection over the pricing attribute tables, resolving coded identifiers into descriptive attribute names and values through Advanced Pricing APIs. This makes it valuable when investigating why a particular qualifier was or was not matched during pricing engine evaluation, and when extracting qualifier definition data for external systems or custom reporting.

Underlying Base Objects

The view is defined over the following documented base objects:

• QP_RLTD_MODIFIERS (synonym) — supplies the modifier relationship rows. The join filters on rltd_modifier_grp_type = 'QUALIFIER' and links to_rltd_modifier_id to the pricing attribute's list line.
• QP_PRICING_ATTRIBUTES (synonym) — supplies the product, pricing attribute context, attribute values, UOM, comparison operator, and audit columns.
• MTL_UNITS_OF_MEASURE (synonym) — an outer-joined lookup (via product_uom_code = uom_code (+)) that translates the stored UOM code into its descriptive unit of measure.
• QP_QP_FORM_PRICING_ATTR (package) — provides Get_Attribute and Get_Attribute_Value functions that resolve attribute context and attribute identifiers against the 'QP_ATTR_DEFNS_PRICING' attribute definition set.
• QP_PRICE_LIST_LINE_UTIL (package) — provides get_product_value, used to resolve the product attribute value from the definition set.

Notably, the user's search term "qp_attr_defns_pricing" corresponds to the attribute definition set name passed as the first argument to these API calls, confirming that the view resolves its descriptive attribute names and values from that definition source.

Key Columns

• FROM_RLTD_MODIFIER_ID / TO_RLTD_MODIFIER_ID — the related modifier relationship endpoints; the TO identifier joins to the pricing attribute list line.
• PRODUCT_ATTRIBUTE_CONTEXT and the resolved product attribute name/value — the context and descriptive value of the buy product attribute.
• PRICING_ATTRIBUTE_CONTEXT, PRICING_ATTRIBUTE, PRICING_ATTR_VALUE_FROM / _TO — the pricing attribute definition, with resolved names and range values.
• PRODUCT_UOM_CODE / UNIT_OF_MEASURE — coded and descriptive units of measure for the product attribute.
• COMPARISON_OPERATOR_CODE and its lookup meaning — the operator (e.g., equals, between) governing qualification.
• RLTD_MODIFIER_GRP_NO — the relationship group number.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.
• ORIG_SYS_PRICING_ATTR_REF — the originating system reference for the pricing attribute, supporting multi-source data lineage.

Common Use Cases and Queries

Typical scenarios include auditing qualifier definitions for promotions, verifying attribute resolution when the pricing engine produces unexpected results, and feeding qualifier data into custom reports or downstream integrations.

SELECT from_rltd_modifier_id,
       to_rltd_modifier_id,
       product_attribute_context,
       pricing_attribute_context,
       pricing_attribute
FROM   apps.qpfv_additional_buy_products
WHERE  to_rltd_modifier_id = :modifier_id;

Filtering by to_rltd_modifier_id isolates the qualifier attributes attached to a specific modifier, while grouping by rltd_modifier_grp_no supports analysis of multi-line qualifier groups. Because the view is declared WITH READ ONLY, it is safe for concurrent query access and cannot be used for DML.