Search Results qp_debug_req_pri_line_attrs_v




Overview
Explore in AI Chat

Overview

QP_DEBUG_REQ_PRI_LINE_ATTRS_V is a diagnostic view owned by the APPS schema in Oracle E-Business Suite, belonging to the QP (Advanced Pricing) product family. It is a filtered projection of the underlying debug table QP_DEBUG_REQ_LINE_ATTRS, restricted to rows where ATTRIBUTE_TYPE equals 'PRICING'. The view exposes the pricing attributes that the attribute mapping functionality supplied to the pricing engine during a pricing request. The pricing engine consumes these attributes to qualify a line or an order for benefits such as discounts, modifiers, surcharges, and price list lines. Because the object is a view rather than a table, it carries no independent storage and is always VALID against its base synonym. The view is intended exclusively for troubleshooting and analysis, not for transactional processing. It is particularly valuable when investigating why a pricing rule did or did not fire, since it records both the attribute values passed in and the qualification outcome recorded by the engine.

Underlying Base Objects

The view is defined over a single referenced base object, QP_DEBUG_REQ_LINE_ATTRS, which is exposed in the APPS schema as a synonym. The defining query selects a fixed column list plus ROWID (aliased as ROW_ID) from that table and applies the predicate WHERE ATTRIBUTE_TYPE = 'PRICING'. This predicate is the essential differentiator: the base table stores attributes of multiple types generated during a pricing request, and the view narrows the result set to those the attribute mapping layer classified as pricing attributes. Each row therefore corresponds to one attribute considered by the pricing engine for a specific line or line detail within a specific concurrent request.

Key Columns

  • REQUEST_ID – Identifies the pricing request (debug session) that generated the row; used to group all attributes captured during a single engine invocation.
  • LINE_INDEX / LINE_DETAIL_INDEX – Position the attribute within the order line and its detail (such as a price break or qualifier breakdown).
  • LINE_ATTRIBUTE_ID – Unique identifier for the attribute occurrence within the request.
  • ATTRIBUTE_LEVEL / ATTRIBUTE_TYPE – Indicate the qualification scope and category; ATTRIBUTE_TYPE is always 'PRICING' in this view.
  • LIST_HEADER_ID / LIST_LINE_ID – Point to the price list header and line being evaluated.
  • CONTEXT / ATTRIBUTE – Name the descriptive flexfield context and the specific pricing attribute being passed.
  • VALUE_FROM / SETUP_VALUE_FROM / SETUP_VALUE_TO – Show the incoming runtime value alongside the setup values defined for the pricing rule.
  • COMPARISON_OPERATOR_TYPE_CODE – The operator used to compare the runtime value with setup values.
  • APPLIED_FLAG / PRICING_STATUS_CODE / PRICING_STATUS_TEXT – Record whether the attribute qualified and the resulting status.
  • DATATYPE / PROCESSED_CODE – Describe the attribute data type and processing state.
  • PRIMARY_UOM_FLAG – Indicates whether the attribute is expressed in the item's primary unit of measure, which is significant when UOM conversion affects qualification.

Common Use Cases and Queries

This view is used mainly to audit attribute mapping and diagnose qualification failures. A typical query lists all pricing attributes for a given request:

  • SELECT request_id, line_index, attribute, value_from, applied_flag, pricing_status_text FROM qp_debug_req_pri_line_attrs_v WHERE request_id = :request_id ORDER BY line_index, line_detail_index;
  • To isolate attributes flagged in primary UOM: SELECT * FROM qp_debug_req_pri_line_attrs_v WHERE primary_uom_flag = 'Y';
  • To find attributes that were passed but not applied: SELECT attribute, value_from, pricing_status_code FROM qp_debug_req_pri_line_attrs_v WHERE applied_flag = 'N';

Because the view depends on debug data populated only when pricing debug is enabled, results are diagnostic snapshots rather than a permanent audit trail.