Results for “qpfv_product_exclusions”

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

Overview

QPFV_PRODUCT_EXCLUSIONS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Oracle Advanced Pricing (QP) module. It is documented as VALID in both release 12.1.1 and 12.2.2. The view presents information about products that have been explicitly excluded from an Advanced Pricing modifier, such as a price list, discount, surcharge, or promotion. In the pricing engine, a modifier normally applies to a defined set of products or product hierarchies; the exclusion records surfaced by this view represent the inverse — product entries flagged so that the modifier does not apply to them.

Because the view is marked WITH READ ONLY, it functions strictly as an inquiry and reporting object. It is intended for concurrent programs, custom reports, OAF/Forms-based inquiry pages, and integration extracts that need to identify excluded product assignments without navigating the underlying pricing attribute structures. Its primary role in reporting and integration is to flatten modifier exclusion data into a human-readable form by resolving the pricing attribute context and attribute value into descriptive text through the packaged helper functions described below.

Underlying Base Objects

The view is defined over three documented objects:

• QP_PRICING_ATTRIBUTES (SYNONYM) — The driving base object. It stores the pricing attribute rows that qualify or exclude products from modifiers. The view filters this table with the predicate EXCLUDER_FLAG = 'Y', so only exclusion rows are returned.
• QP_QP_FORM_PRICING_ATTR (PACKAGE) — Supplies the GET_ATTRIBUTE function, which resolves the internal PRODUCT_ATTRIBUTE code against the attribute definitions in QP_ATTR_DEFNS_PRICING and the supplied PRODUCT_ATTRIBUTE_CONTEXT, returning the descriptive attribute name for display.
• QP_PRICE_LIST_LINE_UTIL (PACKAGE) — Supplies GET_PRODUCT_VALUE, which resolves the product attribute value code (PRODUCT_ATTR_VALUE) into a meaningful product or value description using the same attribute definition context. This is the function that turns a stored ID or code into a recognizable product name.

The view performs no joins to other pricing tables; all enrichment is achieved through these two package function calls, making the base relationship a single-table filter with two scalar function projections.

Key Columns

• LIST_LINE_ID — Identifier of the pricing list line to which the exclusion applies, linking the row to its parent modifier line.
• EXCLUDER_FLAG — Always 'Y' in this view, indicating the row represents an exclusion. This is the filter predicate that defines the view's purpose.
• PRODUCT_ATTRIBUTE_CONTEXT — The attribute context under which the product attribute is defined; this is the column referenced in the user's search term and is passed as the second argument to both helper functions.
• PRODUCT_ATTRIBUTE — The internal code identifying the product attribute used for the exclusion (e.g., item, item category).
• PRODUCT_ATTR_VALUE — The specific value of the attribute being excluded, such as an inventory item or category identifier.
• LIST_HEADER_ID — Identifier of the parent list or modifier header.
• PRICING_ATTRIBUTE_ID — Unique identifier of the pricing attribute row in the base table.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns.
• _DF — Descriptive flexfield context descriptor column, set to '_DF:QP:QP_PRICING_ATTRIBUTES:QP_PRICING_ATTRIBUTES'.

Common Use Cases and Queries

Typical scenarios include auditing which products are excluded from a given price list, reconciling modifier setup during pricing implementations, and extracting exclusion data for downstream systems. A representative query retrieving all exclusions for a specific list header:

• SELECT list_line_id, product_attribute_context, product_attribute, product_attr_value FROM qpfv_product_exclusions WHERE list_header_id = :p_list_header_id;
• Filtering by context: SELECT * FROM qpfv_product_exclusions WHERE product_attribute_context = 'ITEM';
• Auditing recent changes: SELECT * FROM qpfv_product_exclusions WHERE last_update_date > SYSDATE - 30;

Because the descriptive product and attribute names are produced by package functions rather than stored columns, queries should account for the associated function-call overhead when processing large volumes.