Search Results qp_con_util




Overview
Explore in AI Chat

Overview

QP_CON_UTIL is a utility package in the Oracle E-Business Suite Advanced Pricing (QP) module, owned by the APPS schema. In EBS 12.1.1 and 12.2.2 it provides the low-level, generic data-manipulation layer used by the pricing engine when it must create, amend, or remove rows in the pricing context and attribute structures, particularly during the derivation and evaluation of pricing attributes. Rather than exposing pricing business rules, the package encapsulates reusable row operations — record initialization, attribute translation, and the standard insert/update/delete/query/lock cycle — so that higher-level packages such as QP_ATTRIBUTES_PUB, QP_ATTRIBUTES_PVT, QP_DEFAULT_CON, and QP_QP_FORM_CON can manipulate pricing data consistently. It is classified as a UTIL API, meaning it is not intended as an end-user or public integration entry point but as internal shared infrastructure. It is referenced by four other packages and itself depends on QP_ATTRIBUTES_PUB, FND_API, and the STANDARD library.

Key Procedures and Functions

  • CLEAR_DEPENDENT_ATTR — clears or resets attributes that depend on another attribute's value, maintaining consistency when a driving attribute changes.
  • APPLY_ATTRIBUTE_CHANGES — applies accumulated attribute modifications to the in-memory or persistent pricing record.
  • COMPLETE_RECORD — finalizes a record by populating any remaining mandatory or derived fields before it is committed.
  • CONVERT_MISS_TO_NULL — converts "missing" or placeholder values (for example, the missing-value sentinel used by pricing forms and attribute screens) into nulls.
  • UPDATE_ROW — performs the update of an existing pricing context/attribute row.
  • INSERT_ROW — inserts a new pricing row.
  • DELETE_ROW — removes a pricing row.
  • QUERY_ROW — retrieves a row for reading or validation.
  • LOCK_ROW — acquires a row lock to serialize concurrent modification.
  • GET_VALUES — returns the set of values associated with a pricing context or attribute definition.
  • GET_IDS — returns the corresponding identifiers for those values.

Tables Accessed

The package works against the pricing context base and translation tables through APPS synonyms:

  • QP_PRC_CONTEXTS_B — the base table holding pricing context definitions; read and maintained by the row-level operations.
  • QP_PRC_CONTEXTS_TL — the translation table supplying language-specific context text; joined to satisfy multilingual display and validation.
  • FND_LANGUAGES — the installed-language repository, used to determine the active language when resolving translated context values.

Usage Notes

QP_CON_UTIL is not typically invoked directly by customers. It is called by the pricing attribute and defaulting packages listed above, which in turn are driven by Oracle Pricing forms (for example the pricing context and attribute setup screens referenced by QP_QP_FORM_CON), the pricing engine during attribute derivation, and any custom code that programmatically maintains pricing contexts. When extending Advanced Pricing, developers should prefer the documented public packages (such as QP_ATTRIBUTES_PUB) and treat QP_CON_UTIL as internal. Because it relies on FND_API for the standard API return-status convention, callers should expect error handling through the FND message stack rather than raw exceptions. Row-level operations such as LOCK_ROW and UPDATE_ROW should be used together within a single transaction to preserve concurrency control.