Search Results qp_debug_req_qual_line_attrs_v




Overview
Explore in AI Chat

Overview

QP_DEBUG_REQ_QUAL_LINE_ATTRS_V is a diagnostic view in the Oracle E-Business Suite Advanced Pricing (QP) module, owned by the APPS schema. It is a filtered projection of the pricing debug infrastructure used by the pricing engine, presenting only those records whose ATTRIBUTE_TYPE equals QUALIFIER. The view captures the qualifier attributes that the attribute mapping functionality passed to the pricing engine during a pricing request. The pricing engine evaluates these attributes to determine whether a line or an order qualifies for a given price list, modifier, or qualifier rule.

Because it is a debug view, its role is not transactional but investigative. It provides visibility into the intermediate state of qualifier attribute resolution for a specific pricing request. Developers, functional analysts, and support engineers use it to trace how source document values (such as order line attributes or header attributes) were mapped, transformed, and compared against setup qualifier values. This makes it a primary reference point when diagnosing unexpected pricing results — for example, when a qualifier that should have matched a transaction did not, or when a qualifier incorrectly applied.

The view is defined as valid in the APPS schema and is portable across Oracle EBS 12.1.1 and 12.2.2, since it relies on the core QP debug table structures rather than any release-specific online page or OA framework object.

Underlying Base Objects

The view is built directly over QP_DEBUG_REQ_LINE_ATTRS, which is exposed in the APPS schema as a synonym. This base table stores the working set of attributes generated for a pricing request, including both qualifier and other attribute types. The view applies a single restricting predicate, WHERE ATTRIBUTE_TYPE='QUALIFIER', so consumers receive only the qualifier subset without needing to add the filter themselves.

The view selects an explicit column list rather than SELECT *, which insulates dependent code from column additions to the base table. It exposes ROWID as ROW_ID, a common Oracle convention. No joins or aggregations are present; the view is a straight filter-and-project over its base object, so it inherits the base table's commit timing and lifecycle, which are tied to the pricing debug session (typically keyed by REQUEST_ID).

Key Columns

Common Use Cases and Queries

A typical troubleshooting query isolates a single debug request and inspects qualifier evaluation order and outcomes:

SELECT request_id, line_index, attribute, value_from, setup_value_from, setup_value_to, comparison_operator_type_code, validated_flag, applied_flag, pricing_status_text FROM qp_debug_req_qual_line_attrs_v WHERE request_id = :p_request_id ORDER BY line_index, qualifier_precedence;

To identify qualifiers that failed validation or were not applied:

SELECT request_id, line_index, attribute, pricing_status_text FROM qp_debug_req_qual_line_attrs_v WHERE validated_flag = 'N' OR applied_flag = 'N';

Because the view is read-only and diagnostic, it should be used for analysis only, not as a source for production pricing logic. Records reflect a point-in-time debug snapshot and may be purged according to the debug data retention policy.