Search Results qp_qualifier_rules




Overview

QP_QUALIFIER_RULES is a table in the QP (Advanced Pricing) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the header information for all qualifier rules defined within the Advanced Pricing module. In the pricing engine, a qualifier rule acts as the master definition that determines whether a pricing modifier, discount, surcharge, or promotion is eligible to be applied to a given transaction line. Each row in QP_QUALIFIER_RULES represents one such rule header, with the associated qualifying conditions and criteria held in child tables. The table is owned by the QP schema and is documented as VALID in the ETRM reference for release 12.2.2.

From a data modeling perspective, the heuristic Data Vault classification of this table is hub-leaning. This suggests that QP_QUALIFIER_RULES functions primarily as a central entity or hub keyed by its surrogate identifier, with several dependent tables referencing it as a foreign-key parent rather than being purely transactional or historical in nature. Analysts designing a vault or dimensional model around pricing qualifiers may therefore treat this object as a foundational entity from which links and satellites are derived.

Key Information Stored

The table contains 28 documented columns, dominated by the standard EBS WHO columns and a set of descriptive and flexfield attributes. The most significant columns are:

  • QUALIFIER_RULE_ID — the surrogate primary key, enforced by the unique index QP_QUALIFIER_RULES_PK. This is the single documented unique business-key candidate and is the column referenced by all downstream foreign keys.
  • NAME — the human-readable identifier for the qualifier rule, used throughout the pricing setup user interface.
  • DESCRIPTION — free-text description of the rule's purpose.
  • CONTEXT — the descriptive flexfield context that determines which attribute columns are meaningful for a given row.
  • ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments that capture customer-specific or installation-specific rule metadata.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard WHO audit columns recording insert and update provenance.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, LAST_UPDATE_LOGIN — concurrency and concurrent-program tracking columns that record which program created or last modified the rule.

The distinction between the surrogate key and any business key is important: QUALIFIER_RULE_ID is a system-generated identifier, whereas NAME carries the functional identity of the rule for users. No separate unique constraint on NAME is documented.

Common Use Cases and Queries

Typical uses center on auditing pricing setup, tracing which qualifiers drive a given modifier, and migrating pricing configurations between environments. A simple lookup of rule headers uses the primary key:

  • SELECT qualifier_rule_id, name, description FROM qp.qp_qualifier_rules WHERE qualifier_rule_id = :id;
  • Listing all rules by name pattern: SELECT qualifier_rule_id, name FROM qp.qp_qualifier_rules WHERE name LIKE 'VOL%';
  • Joining headers to their qualifier lines via QUALIFIER_RULE_ID to reconstruct a complete rule definition.
  • Reporting on WHO audit columns to identify rules created or modified after a given date for change-control purposes.

Because the table is header-only, meaningful functional reporting requires joining to QP_QUALIFIERS to retrieve the actual conditions and qualifier groups.

Related Objects

The FK metadata identifies several significant dependent objects that reference QP_QUALIFIER_RULES through QUALIFIER_RULE_ID:

Together these relationships confirm the hub-like role of QP_QUALIFIER_RULES as the anchor entity for qualifier rule configuration and integration across Advanced Pricing and Service Contracts.