Search Results qp_qualifier_rules_pub




Overview
Explore in AI Chat

Overview

QP_QUALIFIER_RULES_UTIL is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Advanced Pricing (QP) module and provides the low-level, reusable data-access and record-manipulation logic that underpins the Qualifier Rules functionality. Qualifier rules determine the conditions under which a price modifier, promotion, or qualification group applies — for example, restricting a discount to a specific customer, customer class, or ordering context. Rather than embedding this logic directly in the public API layers, Oracle Advanced Pricing isolates it in a UTIL-class package so that multiple callers can share consistent insert, update, delete, query, lock, and validation behavior against the underlying qualifier rules data model.

The package carries a VALID status in the ETRM 12.2.2 object registry and is classified as a utility package. It does not represent a public, customer-facing API; the public-facing operations are exposed through QP_QUALIFIER_RULES_PUB, which in turn depends upon this utility package. QP_QUALIFIER_RULES_UTIL itself references the FND_API standard package and QP_QUALIFIER_RULES_PUB, and is referenced by QP_DEFAULT_QUALIFIER_RULES, QP_QP_FORM_QUALIFIER_RULES, QP_QUALIFIER_RULES_PUB, and QP_QUALIFIER_RULES_PVT, in addition to recursive references to itself.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions, representing a complete CRUD-and-validation toolkit:

  • CLEAR_DEPENDENT_ATTR — Clears attribute values that depend on other qualifier attributes, ensuring referential consistency when a controlling attribute changes.
  • APPLY_ATTRIBUTE_CHANGES — Propagates attribute modifications across the qualifier rule records, applying the effects of an attribute value change.
  • COMPLETE_RECORD — Populates or defaults missing fields so that a qualifier rule record reaches a complete, valid state prior to persistence.
  • CONVERT_MISS_TO_NULL — Normalizes null or placeholder input values into proper database NULLs, preventing the storage of empty-string artifacts.
  • UPDATE_ROW — Updates an existing qualifier rule row.
  • INSERT_ROW — Inserts a new qualifier rule row.
  • DELETE_ROW — Deletes a qualifier rule row.
  • QUERY_ROW — Retrieves a qualifier rule row by its identifying key.
  • LOCK_ROW — Acquires a row-level lock to support concurrency control during updates and deletes.
  • GET_VALUES — Returns the set of attribute values associated with a qualifier rule.
  • GET_IDS — Returns the internal identifier or identifiers associated with a qualifier rule record.

Tables Accessed

The documented base table referenced through APPS synonyms is QP_QUALIFIER_RULES. This table stores the qualifier rule definitions, including the qualification context, the attribute groups, and the applied operator/values that determine when a pricing modifier or promotion applies. All row-level operations in the package — INSERT_ROW, UPDATE_ROW, DELETE_ROW, QUERY_ROW, and LOCK_ROW — target this table, while GET_VALUES and GET_IDS read the identifying and value data needed to construct, validate, and maintain those rows.

Usage Notes

QP_QUALIFIER_RULES_UTIL is an internal component and is not intended for direct invocation by customers or by general-purpose custom code. It is normally called by higher-level Advanced Pricing objects: QP_QUALIFIER_RULES_PUB (the public API), QP_QUALIFIER_RULES_PVT (the private implementation layer), QP_DEFAULT_QUALIFIER_RULES (used to seed default qualifier rules), and QP_QP_FORM_QUALIFIER_RULES (the Oracle Forms front end). In practice, this means the package is exercised when users define or maintain qualifier rules through the Advanced Pricing forms UI, when concurrent or default-seeding processes create standard qualifier rules, and when the published qualifier rules API is called from integrations or extensions. Because it performs row locks and attribute dependency management, direct use from custom code should be avoided in favor of the public QP_QUALIFIER_RULES_PUB interface, which preserves the documented validation and concurrency behavior.