Results for “qualifier_precedence”

50+ results




Overview
Explore in AI Chat

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

Overview

QP_DEBUG_REQ_PROD_LINE_ATTRS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Advanced Pricing (QP). It is a diagnostic and debugging object that exposes the product-level attributes passed by the attribute mapping functionality to the pricing engine during pricing and qualification requests. In Oracle EBS 12.1.1 and 12.2.2, the pricing engine evaluates these attributes to determine whether an order line or an entire order qualifies for a given price list line, modifier, or qualifier. The view is registered in ETRM with a status of VALID and forms part of the QP debugging infrastructure that supports the Advanced Pricing engine.

Rather than presenting runtime pricing results, this view presents the input payload: the discrete product attributes, their values, and their qualification metadata as they were supplied to the pricing engine. This makes it an essential object for support diagnostics, discrepancy investigation, and troubleshooting why a particular product attribute did not qualify a line for a promotion or price adjustment.

Underlying Base Objects

The view is defined directly over the object QP_DEBUG_REQ_LINE_ATTRS, referenced through a synonym in the APPS schema. The view text applies a fixed filter to that base object:

  • SELECT ... FROM QP_DEBUG_REQ_LINE_ATTRS WHERE ATTRIBUTE_TYPE='PRODUCT'

Because the view is a single-table projection with a constant predicate, it is not updatable through EBS forms; it is strictly a query object. The base table stores line attributes for all attribute types captured during a pricing debug request, and the view narrows that population to the PRODUCT attribute type, which corresponds to product-level qualification attributes such as item, item category, and other inventory or item-related characteristics used by the pricing engine.

Key Columns

  • ROW_ID — the ROWID of the underlying base table row, exposed for unique row identification.
  • REQUEST_ID — the pricing debug request identifier, used to correlate all attributes belonging to a single pricing call.
  • LINE_INDEX / LINE_DETAIL_INDEX — positional identifiers for the line and line detail within the request payload.
  • LINE_ATTRIBUTE_ID — surrogate identifier for the attribute record.
  • ATTRIBUTE_LEVEL — indicates the level at which the attribute is evaluated (for example, line or order header level), which is central to understanding how the pricing engine applied the attribute during qualification.
  • ATTRIBUTE_TYPE — always 'PRODUCT' in this view by virtue of the view predicate.
  • LIST_HEADER_ID / LIST_LINE_ID — identify the price list and price list line against which the attribute was evaluated.
  • CONTEXT / ATTRIBUTE — the descriptive flexfield context and the specific attribute name being passed to the engine.
  • VALUE_FROM / SETUP_VALUE_FROM / SETUP_VALUE_TO — the runtime value and the configured setup range used for qualification matching.
  • APPLIED_FLAG, EXCLUDER_FLAG, QUALIFIER_PRECEDENCE — flags and precedence values indicating whether the attribute was applied, whether it acted as an excluder, and its precedence rank.
  • PRICING_STATUS_CODE / PRICING_STATUS_TEXT — the resulting pricing status assigned after evaluation.
  • DATATYPE, PRODUCT_UOM_CODE, GROUP_QUANTITY, GROUP_AMOUNT, PRIMARY_UOM_FLAG, PROCESSED_CODE — supporting metadata describing the attribute value, the unit of measure, grouping quantities, and processing state.

Common Use Cases and Queries

This view is typically queried during pricing troubleshooting, when a user needs to confirm exactly which product attributes were passed to the pricing engine and how they were qualified. A common approach is to filter by REQUEST_ID to isolate all attributes from a single debug run:

  • SELECT REQUEST_ID, LINE_INDEX, ATTRIBUTE, VALUE_FROM, SETUP_VALUE_FROM, SETUP_VALUE_TO, APPLIED_FLAG, PRICING_STATUS_TEXT FROM APPS.QP_DEBUG_REQ_PROD_LINE_ATTRS_V WHERE REQUEST_ID = :p_request_id ORDER BY LINE_INDEX, LINE_DETAIL_INDEX;
  • Investigating qualification failures: SELECT ATTRIBUTE, VALUE_FROM, APPLIED_FLAG, EXCLUDER_FLAG, QUALIFIER_PRECEDENCE FROM APPS.QP_DEBUG_REQ_PROD_LINE_ATTRS_V WHERE REQUEST_ID = :p_request_id AND APPLIED_FLAG = 'N';
  • Joining to QP_DEBUG_REQ_LINE_ATTRS on REQUEST_ID and LINE_INDEX to compare PRODUCT attributes against other attribute types captured in the same request.

Because it is a diagnostic view, it should not be used as a transactional source for permanent reporting; its content reflects debug captures and is best used transiently during pricing issue analysis.