Search Results comparision_operator_code

Overview

APPS.QP_QUALIFIERS_V is a supplementary view in the Oracle E-Business Suite Advanced Pricing (QP) module. It is classified under ETRM as a VIEW owned by the APPS schema, registered in FND Design Data as QP.QP_QUALIFIERS_V, and reported with a status of VALID. The view exposes qualifier definitions used by Oracle Advanced Pricing to determine whether a modifier, price list line, or promotion applies to a given transaction line. A qualifier defines the condition — for example, a customer, customer group, order type, item, or item category — that must be satisfied before a pricing adjustment or list price is considered valid.

The view is expressly described as a supplementary view that simplifies Oracle Forms coding. Oracle's own documentation warns that this view should not be queried or altered for persistent data operations, because its definition may change dramatically across minor or major releases. Consequently, it is best understood as a developer-facing and Forms-facing construct rather than a stable integration interface. For reporting and integration, QP_QUALIFIERS_V offers a convenient, pre-joined projection of qualifier header data and qualifier rule data, which is otherwise distributed across multiple base tables. This convenience comes at the cost of version stability, so consumers should treat it as a reference implementation rather than a contractual API.

Underlying Base Objects

The documented ETRM metadata for QP_QUALIFIERS_V in release 12.2.2 identifies two referenced base objects:

• QP_QUALIFIERS (SYNONYM) — the primary qualifier definition table.
• QP_QUALIFIER_RULES (SYNONYM) — the qualifier rule definitions associated with those qualifiers.

The view projects columns from QP_QUALIFIERS, including QUALIFIER_ID, QUALIFIER_CONTEXT, QUALIFIER_ATTRIBUTE, QUALIFIER_ATTR_VALUE, and the COMPARISION_OPERATOR_CODE. It projects rule-level columns from QP_QUALIFIER_RULES, including QUALIFIER_RULE_ID, QUALIFIER_GROUPING_NO, QUALIFIER_PRECEDENCE, QUALIFIER_ATTR_VALUE_TO, and RULE_NAME. The relationship is therefore a qualifier-to-rule association, where a single qualifier may be linked to one or more qualifier rules that together express the complete qualifying condition. Because the join is materialized inside the view definition, callers do not need to reconstruct it manually.

Key Columns

• QUALIFIER_ID — Unique identifier of the qualifier record.
• COMPARISION_OPERATOR_CODE — Defines the comparison operator applied to the qualifier attribute value. Note the misspelling in the column name itself, which is the standard Oracle-published spelling for this object.
• QUALIFIER_CONTEXT and CONTEXT — Identify the descriptive flexfield context under which the qualifier is defined.
• QUALIFIER_ATTRIBUTE and QUALIFIER_ATTR_VALUE — Specify the attribute being qualified and its value; QUALIFIER_ATTR_VALUE_TO supports range-style comparisons.
• EXCLUDER_FLAG — Indicates whether the qualifier acts as an inclusion or exclusion condition.
• QUALIFIER_RULE_ID, QUALIFIER_GROUPING_NO, QUALIFIER_PRECEDENCE — Describe rule grouping and evaluation ordering.
• LIST_HEADER_ID and LIST_LINE_ID — Link the qualifier to a price list header and line.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Define the effective date window.
• RULE_NAME and RULE_DESCRIPTION — Human-readable rule identifiers.
• ATTRIBUTE1 through ATTRIBUTE15, plus the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and related audit fields), provide flexible descriptive data and audit tracking.

Common Use Cases and Queries

Typical uses include auditing qualifier-rule pairings, diagnosing why a modifier did or did not qualify on a transaction line, and extracting qualifier definitions for comparison between environments. A representative query isolates qualifiers by their comparison operator:

• SELECT QUALIFIER_ID, QUALIFIER_CONTEXT, QUALIFIER_ATTRIBUTE, COMPARISION_OPERATOR_CODE, QUALIFIER_ATTR_VALUE
• FROM APPS.QP_QUALIFIERS_V
• WHERE COMPARISION_OPERATOR_CODE = '=';

Because the object is a supplementary Forms view, the preferred long-term approach for production reporting is to query QP_QUALIFIERS and QP_QUALIFIER_RULES directly, or to use supported pricing APIs, rather than relying on the view definition remaining constant in future releases.