Results for “qp_qualifier_rules_v”

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

Overview

QP_QUALIFIER_RULES_V is a seeded Oracle EBS Advanced Pricing (QP) view owned by the APPS schema. It presents qualifier rule information by joining the qualifier rule header with its associated qualifier lines, producing a denormalized, read-only projection of pricing qualifier eligibility criteria. The view is documented in ETRM for both 12.1.1 and 12.2.2, and its status is VALID in the APPS schema. As a reporting and integration object, it exposes the complete rule-to-qualifier relationship without requiring callers to navigate the underlying parent/child tables. This makes it suitable for extracting qualification logic used by pricing engine evaluations, for auditing modifier and price list applicability, and for building data extracts for downstream systems. Because it is a view rather than a table, no direct DML is permitted; changes must be made through the base entities and the standard Advanced Pricing forms or APIs.

Underlying Base Objects

The view definition joins two documented base objects: QP_QUALIFIER_RULES (the rule header, aliased QR) and QP_QUALIFIERS (the individual qualifier lines, aliased QQ). Both are exposed through APPS synonyms. The join predicate is QR.QUALIFIER_RULE_ID = QQ.QUALIFIER_RULE_ID, meaning a qualifier rule with N qualifier lines produces N rows in this view. The view is essentially a horizontal merge of header attributes (name, description, context, descriptive flexfield attributes, who-columns, and concurrent request metadata) with line-level qualifier attributes (comparison operator, qualification context and attribute, grouping number, from/to values, effective dates, datatype, and precedence).

Key Columns

• QUALIFIER_RULE_ID — Primary identifier of the qualifier rule; the join key across both base objects.
• NAME / DESCRIPTION — Header-level rule name and description.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment values for the rule header.
• QUALIFIER_ID — Identifier of the individual qualifier line.
• QUALIFIER_CONTEXT / QUALIFIER_ATTRIBUTE — The qualification context and the specific attribute being qualified (for example, a customer, order type, or pricing attribute).
• COMPARISON_OPERATOR_CODE — The operator used to compare the qualifier attribute against its value (for example, equals, between, in).
• QUALIFIER_ATTR_VALUE / QUALIFIER_ATTR_VALUE_TO — The from-value and, where applicable, the to-value bracketing a range qualifier.
• QUALIFIER_GROUPING_NO — Grouping sequence that governs how multiple qualifier lines are combined.
• QUALIFIER_DATATYPE — The datatype applied to the qualifier attribute value. This is the column most relevant to callers searching on that term, since it determines how the from/to values should be interpreted (for example, character, number, or date) during qualification.
• QUALIFIER_PRECEDENCE — Precedence ranking used to resolve competing qualifiers.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date window for the qualifier line.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Standard audit and concurrent program tracking columns inherited from the rule header.

Common Use Cases and Queries

Typical scenarios include auditing which attributes qualify a given pricing rule, extracting qualification logic for reconciliation against a source system, and diagnosing why a modifier did not apply. The QUALIFIER_DATATYPE column is frequently queried to confirm how values should be cast when interpreting a qualifier.

To list all qualifier lines for a named rule:

SELECT qualifier_rule_id, name, qualifier_id, qualifier_context, qualifier_attribute, comparison_operator_code, qualifier_attr_value, qualifier_attr_value_to, qualifier_datatype, qualifier_precedence FROM qp_qualifier_rules_v WHERE name = :rule_name ORDER BY qualifier_precedence;

To examine precedence and datatype across an active rule set:

SELECT qualifier_rule_id, name, qualifier_attribute, qualifier_datatype, comparison_operator_code, qualifier_attr_value, qualifier_attr_value_to FROM qp_qualifier_rules_v WHERE start_date_active <= SYSDATE AND NVL(end_date_active, SYSDATE+1) > SYSDATE ORDER BY name, qualifier_precedence;

Because the view performs no aggregation, consumers should expect multiple rows per rule and should join to pricing modifier or price list entities via QUALIFIER_RULE_ID when correlating qualifiers to the lists and modifiers they govern. All access should respect standard APPS security and MoWaC/operating unit constraints inherited from the underlying pricing setup.