Search Results qp_debug_req_lines

Overview

QP_DEBUG_REQ_LINES is a diagnostic table in the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It records detailed information about the individual lines being priced during a pricing engine request, capturing the intermediate and final values that the pricing engine calculates for each line. Its primary purpose is to support debugging and troubleshooting of pricing behavior, allowing implementers to trace exactly how the pricing engine interpreted a request, what qualifiers were evaluated, which price lists were considered, and what adjustments were applied.

From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning. This suggests it is best understood as a descriptive satellite that captures transient, request-scoped attributes rather than as a hub or link. Each row describes a line within a specific pricing request and is not intended as a long-term master record. Its foreign key to QP_LIST_HEADERS_B further confirms that it hangs off the pricing setup and references master pricing data rather than owning it.

Key Information Stored

The table contains 44 documented columns. The most operationally significant of these are:

REQUEST_ID and REQUEST_TYPE_CODE — identify the pricing engine request and its category, linking related debug lines together.
LINE_ID and LINE_INDEX — the surrogate line identifier and its sequence within the request.
LINE_TYPE_CODE — indicates the type of line being priced (for example, a regular or parent line).
LINE_QUANTITY and LINE_UOM_CODE — the quantity and unit of measure of the line as received.
PRICED_QUANTITY and PRICED_UOM_CODE — the quantity and unit of measure actually used for pricing.
CURRENCY_CODE and UNIT_PRICE — the pricing currency and the resulting unit price.
ADJUSTED_UNIT_PRICE and UPDATED_ADJUSTED_UNIT_PRICE — the unit price after modifier or adjustment application, and the updated figure after recalculation.
LINE_AMOUNT and GROUP_AMOUNT — the extended line amount and the grouped amount for aggregation scenarios.
PRICE_LIST_HEADER_ID — the foreign key to QP_LIST_HEADERS_B, identifying the price list header considered for the line.
PRICING_STATUS_CODE and PRICING_STATUS_TEXT — the outcome of pricing for the line.
PROCESSED_FLAG and VALIDATED_FLAG — flags indicating processing and validation state.
QUALIFIERS_EXIST_FLAG, PRICING_ATTRS_EXIST_FLAG, and PRIMARY_QUALIFIERS_MATCH_FLAG — indicate whether qualifiers, pricing attributes, and primary qualifiers were present or matched.

The documented metadata does not identify a single-column surrogate primary key or a unique index among these columns. In practice, the combination of REQUEST_ID, LINE_ID, and LINE_INDEX serves as the effective business key for locating a specific debug line.

Common Use Cases and Queries

The principal use case is diagnosing unexpected pricing results. A developer or functional analyst identifies the request ID of a failed or incorrect pricing call and retrieves all associated debug lines to reconstruct what the engine did.

Retrieve all debug lines for a request:
SELECT * FROM QP.QP_DEBUG_REQ_LINES WHERE REQUEST_ID = :request_id ORDER BY LINE_INDEX;
Inspect pricing outcomes and status text for a line type:
SELECT LINE_ID, PRICING_STATUS_CODE, PRICING_STATUS_TEXT, UNIT_PRICE, ADJUSTED_UNIT_PRICE FROM QP.QP_DEBUG_REQ_LINES WHERE REQUEST_ID = :request_id;
Check whether qualifiers or pricing attributes affected the result:
SELECT LINE_ID, QUALIFIERS_EXIST_FLAG, PRICING_ATTRS_EXIST_FLAG, PRIMARY_QUALIFIERS_MATCH_FLAG FROM QP.QP_DEBUG_REQ_LINES WHERE REQUEST_ID = :request_id;
Trace which price list was used by joining to the header table:
SELECT d.LINE_ID, l.NAME FROM QP.QP_DEBUG_REQ_LINES d JOIN QP.QP_LIST_HEADERS_B l ON d.PRICE_LIST_HEADER_ID = l.LIST_HEADER_ID WHERE d.REQUEST_ID = :request_id;

Reporting use cases include auditing pricing engine behavior over time, verifying that adjustments produced expected amounts, and supporting performance analysis of pricing requests.

Related Objects

The most significant related objects include:

QP_LIST_HEADERS_B — referenced via QP_DEBUG_REQ_LINES.PRICE_LIST_HEADER_ID; identifies the price list header associated with the priced line.
QP_LIST_LINES — the price list line detail corresponding to the header, useful when reconstructing pricing context.
QP_DEBUG_REQ_HEADERS — the header-level companion table holding request-level debug information.
QP_DEBUG_REQ_LINE_ATTRS — stores pricing attribute detail for the debug lines.
QP_DEBUG_REQ_LINE_QUALIFIERS — stores qualifier detail for the debug lines.
QP_PRICING_ATTRIBUTES — the pricing attribute definitions that influence qualification.
OE_ORDER_LINES_ALL — order lines that may be the source of the pricing request.

These relationships allow analysts to move from a debug line outward to the pricing setup and the source transaction, completing the diagnostic picture.

Table: QP_DEBUG_REQ_LINES 12.1.1
owner:QP, object_type:TABLE, fnd_design_data:QP.QP_DEBUG_REQ_LINES, object_name:QP_DEBUG_REQ_LINES, status:VALID, product: QP - Advanced Pricing , description: This table contains information about the lines being priced. , implementation_dba_data: QP.QP_DEBUG_REQ_LINES ,
Table: QP_DEBUG_REQ_LINES 12.2.2
owner:QP, object_type:TABLE, fnd_design_data:QP.QP_DEBUG_REQ_LINES, object_name:QP_DEBUG_REQ_LINES, status:VALID, product: QP - Advanced Pricing , description: This table contains information about the lines being priced. , implementation_dba_data: QP.QP_DEBUG_REQ_LINES ,
View: QP_DEBUG_REQ_LINES_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:QP.QP_DEBUG_REQ_LINES_V, object_name:QP_DEBUG_REQ_LINES_V, status:VALID, product: QP - Advanced Pricing , description: View that joins QP_DEBUG_REQ_LINES and QP_DEBUG_REQ_RLTD_LINES. It contains information about the lines being priced. , implementation_dba_data: APPS.QP_DEBUG_REQ_LINES_V ,
View: QP_DEBUG_REQ_LINES_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:QP.QP_DEBUG_REQ_LINES_V, object_name:QP_DEBUG_REQ_LINES_V, status:VALID, product: QP - Advanced Pricing , description: View that joins QP_DEBUG_REQ_LINES and QP_DEBUG_REQ_RLTD_LINES. It contains information about the lines being priced. , implementation_dba_data: APPS.QP_DEBUG_REQ_LINES_V ,
Table: QP_LIST_HEADERS_B 12.1.1
owner:QP, object_type:TABLE, fnd_design_data:QP.QP_LIST_HEADERS_B, object_name:QP_LIST_HEADERS_B, status:VALID, product: QP - Advanced Pricing , description: QP_LIST_HEADERS_B stores the header information for all lists. List types can be, for example, Price Lists, Discount Lists or Promotions. , implementation_dba_data: QP.QP_LIST_HEADERS_B ,
Table: QP_LIST_HEADERS_B 12.2.2
owner:QP, object_type:TABLE, fnd_design_data:QP.QP_LIST_HEADERS_B, object_name:QP_LIST_HEADERS_B, status:VALID, product: QP - Advanced Pricing , description: QP_LIST_HEADERS_B stores the header information for all lists. List types can be, for example, Price Lists, Discount Lists or Promotions. , implementation_dba_data: QP.QP_LIST_HEADERS_B ,