Results for “get_modifiers”

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

Overview

QP_MODIFIERS_GRP is a PL/SQL group package in the APPS schema that belongs to the Oracle Advanced Pricing (QP) module of Oracle E-Business Suite. The package is classified as an API of type GRP, indicating that it functions as a gateway or batch-processing layer rather than a low-level business API. Its purpose is to process, lock, and retrieve pricing modifiers — the list-line level adjustment records that represent discounts, surcharges, price breaks, and other promotional or pricing rule effects applied to items, customers, and order lines.

In the Advanced Pricing data model, modifiers are stored on price lists and modifier lists whose headers reside in QP_LIST_HEADERS_B and whose detail lines (including qualifier and pricing attribute groups) reside in QP_LIST_LINES. QP_MODIFIERS_GRP coordinates the bulk handling of these records so that other application modules can consume price adjustments reliably. ETRM documents the package as VALID in the APPS schema and confirms its dependency on FND_API for the Oracle Applications error-handling standard, on QP_GLOBALS for environment and profile constants, on QP_MODIFIERS_PUB for the published modifier API layer, and on QP_QUALIFIER_RULES_PUB for qualifier rule evaluation. The GRP designation and the bulk-oriented procedure names indicate that it is intended for set-based operations over modifier lists rather than single-record maintenance screens.

Key Procedures and Functions

Three documented procedures constitute the public surface of the package:

• PROCESS_MODIFIERS — Drives the main work of the package, applying the modifier definitions held in Advanced Pricing to the context being evaluated. It represents the entry point through which modifier lists are loaded and made available for pricing evaluation, order capture, or offer qualification.
• LOCK_MODIFIERS — Obtains the necessary locking on modifier data so that concurrent processing does not corrupt or misread records during update or write-back operations. It is the concurrency-control companion to PROCESS_MODIFIERS.
• GET_MODIFIERS — Returns the set of modifiers relevant to the calling context, allowing the caller to retrieve processed modifier results without re-invoking the full processing logic.

The full parameter lists are not reproduced here; the published metadata documents only the procedure names. Callers should obtain signatures from the package specification in the database rather than assuming argument order.

Tables Accessed

ETRM records three base tables referenced through APPS synonyms:

• QP_LIST_HEADERS_B — Holds the header definition of each price list or modifier list, including list type, currency, and start/end dates. The package reads this table to identify which modifier lists are active and applicable.
• QP_LIST_LINES — Holds the individual list lines, including modifier lines, qualifiers, and pricing attributes. This is the core detail table the package processes and locks.
• PLITBLM — A DBA/Advanced Pricing table relevant to list-line processing. The package accesses it in support of the retrieval and processing of modifier line data.

Data is read from QP_LIST_HEADERS_B to resolve list identity and written or locked through QP_LIST_LINES during modifier maintenance. Because the package operates on base tables rather than the interface tables used by bulk import, it is appropriate for transactional and in-process pricing behavior, not for concurrent-request imports.

Usage Notes

QP_MODIFIERS_GRP is referenced by OE_BLANKET_PRICING_UTIL and OZF_OFFER_PVT, as well as by itself, per the documented dependency tree. This means the package is invoked indirectly during blanket sales agreement pricing and during Trade Management offer processing, both of which rely on Advanced Pricing modifiers to determine effective prices and promotions. Custom code should generally call the published API layer (QP_MODIFIERS_PUB) for single-record changes, and reserve QP_MODIFIERS_GRP for the set-based processing and locking scenarios it was designed to serve. Because the package depends on FND_API, callers should expect standard FND_API error and message handling conventions and should check the returned status and message stack after invocation. The package is not exposed as a concurrent program in the documented metadata; it is a programmatic component invoked from forms and other PL/SQL units within the same database session.