Results for “satisfied_range_value”

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

Overview

QP_DEBUG_REQ_RLTD_LINES is a diagnostic table in the QP (Advanced Pricing) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It captures information about the related lines produced during pricing engine execution, specifically the relationship between a primary list line and the related list line evaluated against it during a pricing request. The table exists to support debugging and traceability of the Advanced Pricing calculation logic, recording the intermediate operands, qualifier values, relationship types, and range satisfaction results that drive adjustments and price list resolution.

Heuristically, based on the foreign key structure mined from the ETRM metadata, this object is best modeled as a link table. It sits between pricing request execution context and the underlying QP_LIST_LINES definitions, resolving the many-to-many association between a sourced list line and a related list line as processed by the pricing engine. This makes it a natural associative entity in a Data Vault or dimensional model of pricing diagnostics.

Key Information Stored

The table contains 21 documented columns. The most significant include:

• REQUEST_ID and REQUEST_TYPE_CODE — identifier and classification of the pricing debug request that produced the row, tying the record back to a debug session.
• LINE_INDEX, LINE_DETAIL_INDEX, RELATED_LINE_INDEX, RELATED_LINE_DETAIL_INDEX — positional coordinates for the primary line and its related line within the pricing request structure.
• RELATIONSHIP_TYPE_CODE and RELATIONSHIP_TYPE_DETAIL — the nature of the relationship between the primary and related lines.
• LIST_LINE_ID and RELATED_LIST_LINE_ID — the two surrogate foreign keys pointing to QP_LIST_LINES, plus RELATED_LIST_LINE_TYPE.
• PRICING_STATUS_CODE and PRICING_STATUS_TEXT — the evaluation outcome for the relationship.
• OPERAND_CALCULATION_CODE, OPERAND, SETUP_VALUE_FROM, SETUP_VALUE_TO, QUALIFIER_VALUE, ADJUSTMENT_AMOUNT, SATISFIED_RANGE_VALUE — the computed pricing operands, qualifier inputs, adjustment figures, and range-evaluation results.
• PRICING_GROUP_SEQUENCE — the ordering of the line within its pricing group.

The table carries no documented single-column surrogate primary key; the two foreign keys to QP_LIST_LINES (LIST_LINE_ID and RELATED_LIST_LINE_ID) act as the principal business-key link columns.

Common Use Cases and Queries

Typical usage centers on diagnosing why a particular adjustment or price did not fire or produced an unexpected amount.

• Retrieving all related lines for a given debug request: SELECT * FROM QP.QP_DEBUG_REQ_RLTD_LINES WHERE REQUEST_ID = :p_request_id ORDER BY LINE_INDEX, LINE_DETAIL_INDEX;
• Joining to QP_LIST_LINES to resolve list line descriptions for both the source and related line: ... JOIN QP_LIST_LINES L1 ON L1.LIST_LINE_ID = D.LIST_LINE_ID JOIN QP_LIST_LINES L2 ON L2.LIST_LINE_ID = D.RELATED_LIST_LINE_ID;
• Filtering by PRICING_STATUS_CODE to isolate lines whose range qualifiers did or did not satisfy (SATISFIED_RANGE_VALUE).
• Reporting adjustment amounts by PRICING_GROUP_SEQUENCE to reconstruct the sequence in which pricing evaluated related lines.

Because this is a debug table, it is populated only when pricing debug tracing is enabled, so row volume is typically transient and tied to active troubleshooting.

Related Objects

• QP_LIST_LINES — referenced twice via LIST_LINE_ID and RELATED_LIST_LINE_ID; the primary definition source for both lines in the relationship.
• QP_DEBUG_REQ_LINES — the parent debug request line context that the related-line rows belong to (via REQUEST_ID / LINE_INDEX).
• QP_DEBUG_REQ_QUALIFIERS — companion diagnostic table holding qualifier evaluation detail aligned to the same request.
• QP_DEBUG_REQ_LINE_DTLS — detail-level debug records sharing the same request identifiers.
• QP_PRICING_DEBUG_REQUESTS — header table defining the debug request identified by REQUEST_ID.
• QP_LIST_HEADERS_B — header context for the list lines involved.

Together these objects form the pricing debug trace family used to reconstruct the evaluation path through Advanced Pricing.