Search Results arithmetic_operator




Overview
Explore in AI Chat

Overview

APPS.QP_DEBUG_REQ_RLTD_LINES_V is a diagnostic view within the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite. It is designed to expose the internal debug records generated when the pricing engine processes a pricing request, specifically the relationship between pricing request lines and the list line details that were evaluated or referenced during qualification and calculation. The view consolidates two related debug tables — QP_DEBUG_REQ_RLTD_LINES and QP_DEBUG_REQ_LDETS — into a single flat result set, allowing developers and support analysts to trace how pricing attributes, list headers, list lines, and operands were resolved for a given request. It plays a supporting role in reporting and troubleshooting rather than in day-to-day transactional pricing; it is primarily referenced during investigation of pricing engine behaviour, integration debugging, and reproduction of pricing discrepancies.

Underlying Base Objects

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

  • QP_DEBUG_REQ_RLTD_LINES — stores the relationship records linking a debug request to related line detail indexes, including the relationship type code and, in the second branch of the UNION, a related line detail index.
  • QP_DEBUG_REQ_LDETS — stores the detail-level debug rows for each request, including the list header, list type, list line, line type, operand calculation code, and operand value.

The view joins these two objects on REQUEST_ID and on LINE_DETAIL_INDEX. A UNION combines two variants: one where the join uses LINE_DETAIL_INDEX and another where it uses RELATED_LINE_DETAIL_INDEX. This dual-branch construction lets the view present both the primary detail line and any related line detail in a consistent, flattened form.

Key Columns

Common Use Cases and Queries

Typical uses include diagnosing why a particular price was returned, auditing which list lines were evaluated for a request, and extracting debug data for support escalation. A representative query filtering on the list type code is shown below:

  • Retrieve all related lines for a request: SELECT request_id, list_type_code, list_header_id, list_line_id, arithmetic_operator, operand_value FROM apps.qp_debug_req_rltd_lines_v WHERE request_id = :p_request_id;
  • Filter by list type: SELECT * FROM apps.qp_debug_req_rltd_lines_v WHERE list_type_code = :p_list_type;
  • Join back to request metadata to correlate request type with returned lines for full debugging traceability.