Search Results comparision_operator_code

Overview

QP_QUALIFIERS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the Advanced Pricing (QP) product family. In both release 12.1.1 and 12.2.2, the view presents qualifier information used by Oracle Advanced Pricing to determine when a price list, modifier, or promotion applies to a given transaction line. Qualifiers represent the conditions evaluated against pricing and ordering attributes — for example, customer, ordering attributes, item, or context values — that must be satisfied before a pricing rule is executed.

The view is not a standalone transactional entity; it is a denormalized read model that joins the base qualifier data to the qualifier rules that created them. Because it exposes the APPS-schema qualifiers with a consistent, query-ready shape, QP_QUALIFIERS_V is commonly used as a source for custom reports, extract programs, data validation scripts, integrations, and troubleshooting of pricing setup. It is marked VALID and is intended for query access rather than direct DML; inserts and updates should target the underlying base tables.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over two referenced objects, both exposed as synonyms in the view body:

• QP_QUALIFIERS (SYNONYM) — the primary base table holding qualifier definitions, including the qualifier identifier, comparison operator, context and attribute values, active dates, precedence, and who-columns.
• QP_QUALIFIER_RULES (SYNONYM) — the rules table that stores the descriptive rule name and description associated with a qualifier rule.

The join is an outer join from QP_QUALIFIERS to QP_QUALIFIER_RULES on the rule identifier (Q.CREATED_FROM_RULE_ID = R.QUALIFIER_RULE_ID(+)). This means every qualifier row is returned even when no matching rule description exists, with RULE_NAME and RULE_DESCRIPTION returned as null in that case. The view therefore complements the base qualifier table with rule-level descriptive text without restricting the result set.

Key Columns

The view exposes the full column set of QP_QUALIFIERS plus two descriptive columns from QP_QUALIFIER_RULES. Significant columns include:

• QUALIFIER_ID — primary identifier of the qualifier record; the key used in joins to pricing entities.
• EXCLUDER_FLAG — indicates whether the qualifier acts as an exclusion (negative) condition.
• COMPARISON_OPERATOR_CODE — the operator (for example equals, between, greater than) applied to the qualifier attribute value. Note that the ETRM documentation lists the legacy spelling COMPARISION_OPERATOR_CODE in one section while the view text uses COMPARISON_OPERATOR_CODE.
• QUALIFIER_CONTEXT and QUALIFIER_ATTRIBUTE — context and attribute against which the qualifier is evaluated.
• QUALIFIER_ATTR_VALUE and QUALIFIER_ATTR_VALUE_TO — the value (or range end value) used in the comparison.
• QUALIFIER_DATATYPE and QUALIFIER_PRECEDENCE — datatype of the qualifier value and its evaluation precedence.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating for the qualifier.
• LIST_HEADER_ID and LIST_LINE_ID — association to the price list header and line to which the qualifier belongs.
• QUALIFIER_RULE_ID, QUALIFIER_GROUPING_NO, CREATED_FROM_RULE_ID — identifiers linking qualifiers into rules and grouping logic.
• RULE_NAME and RULE_DESCRIPTION — descriptive text from QP_QUALIFIER_RULES, useful for human-readable reporting.
• Standard who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) plus ROWID for auditing and change tracking.

Common Use Cases and Queries

Typical scenarios include auditing qualifier configuration for a price list, reporting active qualifiers by date, reconciling custom pricing logic, and extracting qualifier data for integration or migration. The following sample queries illustrate routine access patterns:

• List active qualifiers for a given price list with their rule descriptions:

  SELECT q.qualifier_id, q.qualifier_context, q.qualifier_attribute,
         q.comparison_operator_code, q.qualifier_attr_value,
         q.start_date_active, q.end_date_active,
         q.rule_name, q.rule_description
  FROM   qp_qualifiers_v q
  WHERE  q.list_header_id = :p_list_header_id
  AND    SYSDATE BETWEEN NVL(q.start_date_active, SYSDATE)
                     AND NVL(q.end_date_active, SYSDATE);
  

• Identify exclusion qualifiers configured in the system:

  SELECT qualifier_id, list_header_id, rule_name
  FROM   qp_qualifiers_v
  WHERE  excluder_flag = 'Y';
  

• Report qualifiers with no associated rule description (outer-join nulls):

  SELECT qualifier_id, qualifier_rule_id
  FROM   qp_qualifiers_v
  WHERE  rule_name IS NULL;
  

Because the view is read-only and exposed in the APPS schema, grant-based access or a custom view against it is recommended for downstream reporting. Queries should filter on list identifiers or effective dates to avoid scanning the full qualifier population.