Search Results qp_debug_req_line_attrs




Overview
Explore in AI Chat

Overview

The QP_DEBUG_REQ_LINE_ATTRS table is a diagnostic and debugging object within the Oracle E-Business Suite Advanced Pricing (QP) module. Its primary role is to serve as a transient repository for detailed attribute data during the price request processing lifecycle. Specifically, it captures the complete set of pricing attributes that the attribute mapping functionality passes to the pricing engine for evaluation. This data is critical for the engine to determine eligibility for price lists, modifiers, promotions, and other benefits by qualifying an order or an order line against complex pricing rules. The table's "DEBUG" nomenclature indicates its primary utility is for troubleshooting, performance analysis, and verifying the accuracy of attribute mapping configurations in implementations such as Release 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and foreign key relationships define its core data structure. It stores a granular record of attribute values associated with a specific pricing request line. Key fields typically include a request identifier linking to the parent debug session, line identifiers, and the attribute details themselves. Crucially, the foreign keys reveal two essential columns: LIST_HEADER_ID and LIST_LINE_ID. These columns link the captured attribute data directly to the specific price list (QP_LIST_HEADERS_B) and price list line (QP_LIST_LINES) being evaluated by the pricing engine, creating a clear audit trail from a pricing benefit back to the raw attributes that qualified the transaction for it.

Common Use Cases and Queries

The principal use case is diagnosing pricing engine behavior when a transaction does not receive an expected discount, surcharge, or price. Analysts and developers query this table to verify which attributes (e.g., customer category, item hierarchy, order type) were actually passed for evaluation and compare them against the conditions defined on the price list line. A common query pattern involves joining to the related list headers and lines tables to isolate attributes for a specific failed pricing scenario. For example:

SELECT d.*, ll.operand FROM qp_debug_req_line_attrs d, qp_list_lines ll WHERE d.list_line_id = ll.list_line_id AND d.request_id = &debug_request_id;

This analysis is vital for resolving configuration errors in attribute mapping rules or misunderstandings in pricing setup.

Related Objects

QP_DEBUG_REQ_LINE_ATTRS is intrinsically linked to core Advanced Pricing entities. As per the documented foreign keys, it has a direct relationship with QP_LIST_HEADERS_B (the price list definition) and QP_LIST_LINES (the individual pricing rules within a list). It is a child table within a broader debugging framework that likely includes a parent request table (such as QP_DEBUG_REQUESTS) to track overall pricing calls. Its data is populated by the attribute mapping engine and consumed by the pricing engine during the qualification phase, making it central to the interaction between these two subsystems.