Results for “net_amount_flag”

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

Overview

QP_PREQ_LDETS_TMP is an APPS-owned, VALID database view within the QP (Advanced Pricing) product family of Oracle E-Business Suite. It exposes the contents of the pricing engine's temporary line-detail work area, and according to the ETRM metadata it "has the information pertaining to the current pricing engine call." In both 12.1.1 and 12.2.2 the view is a runtime artifact of the pricing engine rather than a persistent transaction table: rows are transient and scoped to a single pricing engine invocation.
Because the view is centered on the current call, it is primarily relevant to diagnostics, troubleshooting, and custom extensions that inspect or post-process pricing results. It is not a substitute for the permanent pricing tables (QP_LIST_HEADERS, QP_LIST_LINES, QP_PRICE_ADJUSTMENTS) and should not be treated as a historical record. The user's search term, selling_rounding_factor, corresponds to the SELLING_ROUNDING_FACTOR column exposed by this view, which carries the selling-side rounding information for a pricing line during engine processing.

Underlying Base Objects

The documented base object for this view is QP_PREQ_LDETS_TMP_T, listed as a SYNONYM. The view is defined as a simple projection over that table with a filter predicate; per the documented view text, the WHERE clause is:

• REQUEST_ID = NVL(SYS_CONTEXT('QP_CONTEXT','REQUEST_ID'), 1)

This predicate is the defining behavior of the view: it isolates the rows belonging to the current pricing engine call by reading the request identifier from the QP_CONTEXT application context, defaulting to 1 when the context is not set. Consequently, the view returns only the in-flight working set of detail lines for the active request, and the same physical temporary table may hold data for concurrent requests that the view deliberately hides.

Key Columns

The view projects the full column list of QP_PREQ_LDETS_TMP_T. Documentation explicitly confirms the following columns and their relationships to the pricing engine:

• SELLING_ROUNDING_FACTOR — selling-side rounding factor applied to the line during price calculation.
• ROUNDING_FACTOR — general rounding factor for the pricing line.
• LINE_DETAIL_INDEX / LINE_INDEX — ordering identifiers for the detail line and its parent line within the pricing call.
• LINE_DETAIL_TYPE_CODE / LINE_DETAIL_PBH_TYPE / PRICE_BREAK_TYPE_CODE — classify the detail (for example line versus price break).
• MODIFIER_LEVEL_CODE, CREATED_FROM_LIST_HEADER_ID, CREATED_FROM_LIST_LINE_ID — identify the source list header and line and the modifier level that produced the detail.
• OPERAND_CALCULATION_CODE, OPERAND_VALUE, ADJUSTMENT_AMOUNT, LINE_QUANTITY — the operands and computed adjustment amount for the line.
• PRICING_STATUS_CODE / PRICING_STATUS_TEXT, PROCESSED_FLAG, APPLIED_FLAG, UPDATED_FLAG, SELECTED_VOLUME_ATTR — processing and application state of the pricing detail.
• REQUEST_ID, PRICING_EFFECTIVE_DATE, BASE_CURRENCY_CODE, ORDER_CURRENCY, CURRENCY_DETAIL_ID — request, date, and currency context.
• PRICE_FORMULA_ID, PRICE_ADJUSTMENT_ID, CALCULATION_CODE, LIMIT_CODE — formula, adjustment, and limit references used by the engine.

Common Use Cases and Queries

Because the view is request-context filtered, the most common use is inspecting the current pricing engine call within the same session. A minimal query lists the detail lines and their rounding information:

• SELECT line_detail_index, line_index, line_detail_type_code, rounding_factor, selling_rounding_factor FROM qp_preq_ldets_tmp ORDER BY line_detail_index;

To trace a specific modifier or adjustment, filter by the originating list line or price adjustment:

• SELECT line_detail_index, created_from_list_line_id, price_adjustment_id, operand_calculation_code, operand_value, adjustment_amount FROM qp_preq_ldets_tmp WHERE price_adjustment_id = :adjustment_id;

To review status and error information for lines that failed to process:

• SELECT line_detail_index, pricing_status_code, pricing_status_text, processed_flag, applied_flag FROM qp_preq_ldets_tmp WHERE processed_flag = 'N';

These queries are useful during debugging of pricing behavior, verification of rounding factors, and validation that the expected modifiers were evaluated. Outside the active request, the view generally returns no rows, reinforcing its role as a transient diagnostic window into the pricing engine rather than a reporting source.