Results for “qp_debug_req_ldets_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QP_DEBUG_REQ_LDETS_V is a diagnostic (debug) view in the Oracle Advanced Pricing (QP) module, owned by the APPS schema. It exposes the intermediate results produced by the pricing engine during a pricing request, at the granularity of individual line details. Per the ETRM metadata, the view joins QP_DEBUG_REQ_LDETS and QP_DEBUG_REQ_RLTD_LINES and "contains information about the line details being priced," including "adjustment and discount details for lines, including adjustments and discounts that the pricing engine elimi[nated]." It is not a transactional or reporting entity used by production pricing flows; rather, it is a troubleshooting artifact that lets implementers and support engineers inspect what the engine calculated, applied, or discarded. Because it is a debug object, it is populated only when pricing debug logging is enabled, and its contents are keyed by REQUEST_ID. The user search term "created_from_list_header_id" corresponds directly to a column in this view that records the price list header from which a given line detail originated, which is central to tracing how a list price was sourced.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms: QP_DEBUG_REQ_LDETS and QP_DEBUG_REQ_RLTD_LINES. QP_DEBUG_REQ_LDETS supplies the primary line-detail rows (aliased A in the view text). QP_DEBUG_REQ_RLTD_LINES (aliased B) supplies the related-line linkage used to resolve a parent line detail index. The join is an outer join: A.REQUEST_ID = B.REQUEST_ID (+) and A.LINE_DETAIL_INDEX = B.RELATED_LINE_DETAIL_INDEX (+), so every row from the line-detail table is preserved even when no related-line record exists. The view text also applies SELECT DISTINCT and exposes A.ROWID as ROW_ID, which provides physical row identification that can be useful when correlating debug output back to the underlying table. Column PARENT_LINE_DETAIL_INDEX is derived via NVL(B.LINE_DETAIL_INDEX, A.LINE_DETAIL_INDEX), meaning the related-line value takes precedence and falls back to the line's own index.

Key Columns

• REQUEST_ID — Identifies the pricing debug request; the primary correlation key across the debug tables.
• ROW_ID — Physical ROWID of the underlying QP_DEBUG_REQ_LDETS row.
• LINE_DETAIL_INDEX / PARENT_LINE_DETAIL_INDEX — Sequence of the line detail and its resolved parent, enabling hierarchy reconstruction.
• LINE_DETAIL_TYPE_CODE / PRICE_BREAK_TYPE_CODE — Classify the detail (for example, price break or modifier type).
• CREATED_FROM_LIST_HEADER_ID, CREATED_FROM_LIST_LINE_ID, CREATED_FROM_LIST_LINE_TYPE, CREATED_FROM_LIST_TYPE_CODE — Identify the price list header, line, and type from which the detail originated; the header ID is the object of the user's search.
• MODIFIER_LEVEL_CODE — Indicates whether the adjustment is at line or group level.
• ADJUSTMENT_AMOUNT, OPERAND_VALUE, OPERAND_CALCULATION_CODE — The computed adjustment and the operand used to derive it.
• PRICING_STATUS_CODE / PRICING_STATUS_TEXT — Status of the detail within the pricing run.
• APPLIED_FLAG, AUTOMATIC_FLAG, OVERRIDE_FLAG and related qualifier flags — Indicate how the adjustment behaved during evaluation.
• PRODUCT_PRECEDENCE, INCOMPATABILITY_GRP_CODE, BEST_PERCENT — Support determination of which modifiers were selected or suppressed.

Common Use Cases and Queries

Typical uses include troubleshooting why a price or discount did not appear, auditing modifiers the engine eliminated, and tracing the price list behind a computed line price.

• List all line details for a pricing debug request:
  SELECT request_id, line_detail_index, line_detail_type_code, adjustment_amount, pricing_status_code FROM qp_debug_req_ldets_v WHERE request_id = :req_id;
• Find details sourced from a specific price list header (matching the user's search):
  SELECT request_id, line_detail_index, created_from_list_header_id, created_from_list_line_id, adjustment_amount FROM qp_debug_req_ldets_v WHERE created_from_list_header_id = :list_header_id;
• Inspect modifiers that were not applied:
  SELECT line_detail_index, pricing_status_code, pricing_status_text, adjustment_amount FROM qp_debug_req_ldets_v WHERE request_id = :req_id AND applied_flag = 'N';
• Reconstruct parent/child line detail relationships using PARENT_LINE_DETAIL_INDEX.

Because the view depends on debug data being written first, queries return rows only for requests that were logged with pricing debug enabled. On both 12.1.1 and 12.2.2 the definition and columns are consistent with the documented ETRM metadata.