Results for “qp_ldets_v”

50+ results




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

Overview

QP_LDETS_V is an Advanced Pricing (QP) view owned by the APPS schema. As documented in the Oracle E-Business Suite Electronic Technical Reference Manual (ETRM) for releases 12.1.1 and 12.2.2, its stated purpose is to provide Order Management (OM) with the post-pricing adjustment and modifier details produced by the pricing engine. Following Oracle Advanced Pricing calculation, the engine records the modifiers and price adjustments that were applied to a line, and this view exposes those results in a form that the ordering application can consume during order capture, repricing, and order line processing.

The view is not a standalone pricing entity. It is a filtered, joined presentation whose rows represent priced line details still pending final processing. The join predicate on the query text restricts output to records where PRICING_STATUS_CODE equals 'N', and the view therefore functions as a staging interface between the pricing engine's temporary detail records and the consuming order management flow. It is typically read by internal Oracle code rather than being a primary end-user reporting object, though it is available for diagnostic and extension queries.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: QP_LIST_LINES, exposed through a synonym, and QP_PREQ_LDETS_TMP_T, also exposed through a synonym. The view is defined as a join between QP_PREQ_LDETS_TMP (the temporary working storage of priced line details, aliased as A) and QP_LIST_LINES (the modifier or price list line definitions, aliased as B).

The join condition links A.CREATED_FROM_LIST_LINE_ID to B.LIST_LINE_ID, meaning each output row is anchored to the list line that gave rise to the adjustment. Because QP_LIST_LINES holds the modifier setup such as benefit, accrual, proration, and rebate attributes, the view blends runtime calculation results (from the temporary detail table) with configuration data (from the list lines). The QP_PREQ_LDETS_TMP_T synonym maps to the underlying temporary table populated during the pricing request; its rows are transient and scoped to the pricing and order capture cycle.

Key Columns

Common Use Cases and Queries

The most frequent use is diagnosing why a specific modifier did or did not apply to an order line, and inspecting the resulting adjustment amount and pricing phase. The obligatory filter on PRICING_STATUS_CODE = 'N' means the view returns only unprocessed detail records, so it is most useful during or immediately after a pricing request. A representative query follows:

  • SELECT line_index, line_detail_index, list_line_id, modifier_level_code, adjustment_amount, applied_flag, pricing_status_code FROM qp_ldets_v WHERE line_index = :p_line_index;
  • SELECT l.list_line_no, l.adjustment_amount, l.operand_value, l.calculation_code, l.limit_code, l.accrual_flag, l.estm_gl_value FROM qp_ldets_v l WHERE l.created_from_list_header_id = :p_list_header_id ORDER BY l.pricing_group_sequence;

These queries support pricing troubleshooting, verification of modifier sequencing across pricing phases, and reconciliation of accrual and benefit information against the originating list lines.