Results for “uom_name”

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

Overview

QPFV_PRODUCTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the QP (Advanced Pricing) product family. It exposes the pricing attribute rows that define a "Buy" product within a modifier, or the product side of a price list line, and is available in both 12.1.1 and 12.2.2. The view is defined with a WITH READ ONLY clause, which means it is exposed strictly as a query surface and cannot be used as a DML target.

The central role of the view is to translate the low-level, generic attribute storage of QP_PRICING_ATTRIBUTES into product-level information that is meaningful to reporting and integration consumers. Pricing attributes in QP are stored flexibly — the meaning of each row depends on a context and an attribute name — so the view calls QP_QP_FORM_PRICING_ATTR.GET_ATTRIBUTE and QP_PRICE_LIST_LINE_UTIL.GET_PRODUCT_VALUE to resolve the attribute definition and the product value into usable strings. The view also joins to units of measure so that the product UOM is presented alongside its description, and it filters rows so that only non-excluded pricing attributes whose context is null or 'VOLUME' are returned.

Underlying Base Objects

The view is defined over two base objects and two PL/SQL packages, as documented for 12.2.2:

• QP_PRICING_ATTRIBUTES (accessed via a synonym, aliased PA) — the primary driver, holding the pricing attribute context, attribute name, attribute value, product UOM code, and the associated list line and list header identifiers.
• MTL_UNITS_OF_MEASURE (accessed via a synonym, aliased MTL) — joined with an outer join (MTL.UOM_CODE (+)) on PA.PRODUCT_UOM_CODE = MTL.UOM_CODE to supply the UOM description.
• QP_PRICE_LIST_LINE_UTIL (package) — invoked to resolve the product value for a given context, attribute, and attribute value using GET_PRODUCT_VALUE.
• QP_QP_FORM_PRICING_ATTR (package) — invoked to resolve the attribute description using GET_ATTRIBUTE.

Because the UOM join is an outer join, rows with a product UOM code that is not present in MTL_UNITS_OF_MEASURE are still returned, with a null UOM name. The filter requirement PA.EXCLUDER_FLAG = 'N' removes excluded attributes, and the context restriction (null or 'VOLUME') narrows the result to the relevant pricing context.

Key Columns

• PRODUCT_ATTRIBUTE_CONTEXT — the context in which the product pricing attribute is defined (null or 'VOLUME').
• PRODUCT_ATTRIBUTE — the pricing attribute name, resolved to a description by GET_ATTRIBUTE.
• PRODUCT_ATTR_VALUE — the raw attribute value, resolved through GET_PRODUCT_VALUE.
• PRODUCT_UOM_CODE — the unit of measure code held on the pricing attribute row.
• UOM_NAME — the UOM description obtained from MTL_UNITS_OF_MEASURE.
• LIST_LINE_ID, LIST_HEADER_ID — the price list line and price list header to which the product attribute belongs.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.
• _DF — a descriptor flexfield column ('_DF:QP:QP_PRICING_ATTRIBUTES:PA'), used by Oracle Forms to identify the descriptive flexfield context.

Common Use Cases and Queries

The view is typically used to report the products attached to price lists and modifiers, or to resolve the attribute context behind a pricing setup. A basic query lists products for a price list header:

SELECT product_attribute, product_attr_value, product_uom_code, uom_name
FROM apps.qpfv_products
WHERE list_header_id = :p_list_header_id;

To find products by UOM or attribute:

SELECT list_header_id, list_line_id, product_attribute, product_attr_value
FROM apps.qpfv_products
WHERE product_uom_code = :p_uom
AND product_attribute = :p_attr;

Because the view resolves attribute and product values through the QP utility packages, it is also useful for integration code validating that a pricing attribute row maps to a recognized product definition. Joins back to QP_PRICING_ATTRIBUTES on LIST_LINE_ID and LIST_HEADER_ID are common when additional columns, such as EXCLUDER_FLAG or the unpivoted attribute ID, are required.