Search Results qp_debug_req_rltd_lines_v




Overview
Explore in AI Chat

Overview

QP_DEBUG_REQ_RLTD_LINES_V is a diagnostic view owned by the APPS schema within the Oracle E-Business Suite Advanced Pricing (QP) module. It is defined over the pricing debug request tables and exposes the relationship structure between line details captured during a pricing engine debug run. The view is part of the pricing debugger infrastructure, a facility used to trace how the Oracle Advanced Pricing engine resolves lists, formulas, qualifiers, and related line calculations during request processing. Because the debug tables persist intermediate pricing resolution steps, this view provides a normalized projection of those steps suitable for reporting and troubleshooting.

The view is a UNION of two queries against the same pair of base objects, combining rows where the debug line detail index matches either the primary line detail index or the related line detail index. This dual projection ensures that both sides of a pricing relationship are represented in a single result set, which is valuable when analyzing how an adjustment or list line is linked to other lines in the same request.

Underlying Base Objects

The view is defined over two documented base objects, both synonyms in the APPS schema:

  • QP_DEBUG_REQ_RLTD_LINES — stores the relationship records between line detail entries within a debug request, including the line detail index and related line detail index along with the relationship type code.
  • QP_DEBUG_REQ_LDETS — stores the line detail attributes, including list header, list type, list line identifiers, line type, operand calculation code, and operand value.

The join is performed on REQUEST_ID and on LINE_DETAIL_INDEX (first branch) or RELATED_LINE_DETAIL_INDEX (second branch), with the two branches combined by UNION. Columns selected from QP_DEBUG_REQ_RLTD_LINES include REQUEST_ID, REQUEST_TYPE_CODE, LINE_INDEX, LINE_DETAIL_INDEX, and RELATIONSHIP_TYPE_CODE. Columns selected from QP_DEBUG_REQ_LDETS are aliased into the view, notably CREATED_FROM_LIST_HEADER_ID as LIST_HEADER_ID, CREATED_FROM_LIST_TYPE_CODE as LIST_TYPE_CODE, CREATED_FROM_LIST_LINE_ID as LIST_LINE_ID, CREATED_FROM_LIST_LINE_TYPE as LIST_LINE_TYPE_CODE, OPERAND_CALCULATION_CODE as ARITHMETIC_OPERATOR, and OPERAND_VALUE.

Key Columns

  • REQUEST_ID — Identifier of the debug request; the primary correlation key across the underlying tables.
  • REQUEST_TYPE_CODE — Classifies the debug request type.
  • LINE_INDEX — Index of the parent line within the request.
  • LINE_DETAIL_INDEX — The line detail index, taken from either the primary or related index depending on the UNION branch.
  • RELATIONSHIP_TYPE_CODE — Describes the nature of the relationship between the line detail and its related line detail.
  • LIST_HEADER_ID — The pricing list header from which the line was created or resolved.
  • LIST_TYPE_CODE — The type of the pricing list (for example, price list, discount list, or promotion). This is a frequently queried attribute when filtering debug output by list category.
  • LIST_LINE_ID — The specific list line identifier associated with the detail.
  • LIST_LINE_TYPE_CODE — Classification of the list line.
  • ARITHMETIC_OPERATOR — The operand calculation code, indicating the arithmetic applied to the operand value.
  • OPERAND_VALUE — The numeric operand used in the calculation.

Common Use Cases and Queries

This view is used primarily by technical consultants and support analysts diagnosing pricing behavior. Typical scenarios include tracing which list lines contributed to a calculated price, identifying the relationship type between line details, and examining the arithmetic operator and operand values applied. A common filter is by LIST_TYPE_CODE to isolate a particular category of pricing list.

SELECT request_id,
       line_index,
       line_detail_index,
       relationship_type_code,
       list_header_id,
       list_type_code,
       list_line_id,
       arithmetic_operator,
       operand_value
  FROM apps.qp_debug_req_rltd_lines_v
 WHERE request_id = :p_request_id
   AND list_type_code = :p_list_type_code
 ORDER BY line_index, line_detail_index;

Because the view frequently returns multiple rows per line detail due to the UNION, queries should be ordered and, where necessary, de-duplicated to present a readable diagnostic trail. The view is read-only and intended for query and reporting purposes only; no DML should be issued against it or its underlying debug tables outside the standard pricing debugger processes.