Search Results comparison_operator_type_code




Overview
Explore in AI Chat

Overview

APPS.QP_DEBUG_REQ_QUAL_LINE_ATTRS_V is an Oracle E-Business Suite Advanced Pricing (Oracle Pricing / ETRM) diagnostic view that exposes the qualifier-attribute rows captured during pricing engine request processing. It is defined as a restricted projection of the debug line-attribute table, returning only rows where ATTRIBUTE_TYPE equals 'QUALIFIER'. In this sense, the view serves as a focused lens on how the pricing engine evaluated qualifier conditions — the attribute comparisons that determine whether a modifier list line or price list line is applicable to a given request line. The view is intended for debugging, reconciliation, and troubleshooting of pricing behavior rather than for transactional data entry. Because the underlying table records the internal request-evaluation state, the view retains REQUEST_ID, LINE_INDEX, and LINE_DETAIL_INDEX, allowing a DBA or pricing analyst to trace a specific pricing call through its qualifier evaluation steps. Typical consumers include Oracle Support, implementation consultants diagnosing modifier non-application, and custom reports that audit qualifier setup against runtime outcomes in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the synonym QP_DEBUG_REQ_LINE_ATTRS, which resolves to the pricing debug line-attribute table in the APPS schema. The defining text is a simple SELECT with a WHERE predicate restricting ATTRIBUTE_TYPE to 'QUALIFIER'; no joins, unions, or aggregation are present, so the view is a straight filter on the base object. ROWID is exposed as ROW_ID to provide a stable physical identifier. Because the base object also stores other attribute types (for example, pricing attributes used in formula or adjustment contexts), the view effectively partitions the debug data by semantic role, isolating the qualifier subset. The view is read-only in practical terms; it carries Oracle proprietary and confidential classification in the ETRM documentation. Note that the underlying debug table is populated only when pricing debug or diagnostic logging is enabled, so the view generally returns data only for requests executed with that capability active.

Key Columns

Important columns include:

Common Use Cases and Queries

The primary scenario is diagnosing why a modifier or price list line did not apply. Analysts query by REQUEST_ID to reconstruct the qualifier evaluation sequence:

  • SELECT request_id, line_index, list_header_id, list_line_id, context, attribute, value_from, setup_value_from, setup_value_to, comparison_operator_type_code, validated_flag, applied_flag, pricing_status_text FROM apps.qp_debug_req_qual_line_attrs_v WHERE request_id = :req_id ORDER BY line_index, line_detail_index;
  • Comparing operator usage: SELECT comparison_operator_type_code, COUNT(*) FROM apps.qp_debug_req_qual_line_attrs_v GROUP BY comparison_operator_type_code;
  • Finding rejected qualifiers: SELECT * FROM apps.qp_debug_req_qual_line_attrs_v WHERE applied_flag = 'N' AND validated_flag = 'Y';

These queries help confirm whether a mismatch in comparison_operator_type_code or a bound value caused an unexpected qualifier failure, and support regression testing after pricing setup changes across 12.1.1 and 12.2.2.