Search Results qp_preq_lines_tmp




Overview

QP_PREQ_LINES_TMP is an APPS-owned, VALID database view in the QP (Advanced Pricing) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It is a reporting and diagnostic layer over the temporary pricing request data used by the Advanced Pricing engine. The view is described in the ETRM as being "based on QP_PREQ_LDETS_TMP_T" and as holding "the information pertaining to the current pricing engine call." In practice, it exposes the working set of line-level pricing request records that the pricing engine populates and consumes during a single call, such as when a sales order, quote, or pricing request is priced. Because the underlying storage is a temporary table scoped to a REQUEST_ID, the view functions as a snapshot of the lines being evaluated in the active pricing context rather than as a permanent transactional repository.

Underlying Base Objects

The view is defined over a single documented base object, QP_PREQ_LINES_TMP_T, which is accessed through a synonym in the APPS schema. The view text selects from QP_PREQ_LINES_TMP_T (aliased QPT) and applies a critical WHERE predicate:

This predicate restricts the result set to the lines belonging to the current pricing engine call, as identified by the QP_CONTEXT application context. When that context value is not set, the expression defaults to 1, isolating a nominal request ID rather than returning all rows. This behavior is significant for query authors: results depend on session context, so the view is not intended for unfiltered cross-request reporting.

Key Columns

The view projects a broad set of pricing line attributes. Notable columns include:

Common Use Cases and Queries

Typical uses include verifying which lines the pricing engine processed, checking adjustment outcomes and hold conditions, and diagnosing qualification or validation failures during pricing. The view is commonly joined to pricing request headers and to permanent pricing structures for reconciliation. A representative query follows:

  • SELECT line_id, line_index, line_quantity, unit_price, adjusted_unit_price, extended_price, pricing_status_code FROM qp_preq_lines_tmp ORDER BY line_index;
  • SELECT line_id, hold_code, hold_text FROM qp_preq_lines_tmp WHERE hold_code IS NOT NULL;
  • SELECT line_id, price_flag, validated_flag, qualifiers_exist_flag FROM qp_preq_lines_tmp WHERE validated_flag = 'N';

Because access is context-filtered by REQUEST_ID, queries return only the current pricing call's lines; set the QP_CONTEXT REQUEST_ID when targeting a specific call.