Search Results oe_pricing_cont_pub




Overview
Explore in AI Chat

Overview

OE_PRICING_CONT_PVT is a private PL/SQL package in the APPS schema that supports the pricing and agreement functionality of Oracle Order Management within Oracle E-Business Suite 12.1.1 and 12.2.2. The API classification "PVT" indicates that this package is intended for internal use by Oracle's own code rather than as a public integration interface. Its responsibility is to encapsulate the lower-level processing logic that governs pricing contracts, price lists, and agreement qualifiers, which are then exposed to external callers through the companion public package OE_PRICING_CONT_PUB. In practice, OE_PRICING_CONT_PVT acts as the implementation layer beneath the public API, handling record locking, retrieval of contract and pricing context, and the creation and validation of agreement qualifiers used to determine which price list or agreement applies to a given order or line.

The package depends on several Oracle EBS foundation components, including FND_API for the standard API programming model, OE_GLOBALS for Order Management environment settings, and OE_PRICE_LIST_PUB for price list interactions. Together these dependencies confirm that OE_PRICING_CONT_PVT operates within the standard Order Management pricing framework rather than as a standalone utility.

Key Procedures and Functions

The documented API surface consists of four procedures and functions, each serving a distinct role in the pricing contract lifecycle:

  • PROCESS_PRICING_CONT — The primary processing routine. It orchestrates the validation and application of pricing contract data, invoking the supporting logic needed to resolve, evaluate, and persist pricing information for a given context.
  • LOCK_PRICING_CONT — Acquires a lock on the relevant pricing contract record. This is used to serialize concurrent access and prevent conflicting updates during processing, a common pattern in EBS private APIs.
  • GET_PRICING_CONT — Retrieves pricing contract information, returning the current contract data required by callers such as the public API or the Order Management forms.
  • CREATE_AGREEMENT_QUALIFIER — Creates the qualifier records that link an agreement to the conditions under which it applies. Qualifiers in Oracle Advanced Pricing determine the eligibility of a price list or agreement for a specific transaction.

The specific parameter lists for these routines are not exposed in the documented metadata and should not be assumed; developers should inspect the package specification or ETRM's full dependency view for signatures.

Tables Accessed

The package reads and writes several core tables through APPS synonyms, reflecting its role in pricing and agreement management:

  • OE_AGREEMENTS_B — The base table for agreements, holding the agreement header records processed and locked by this package.
  • OE_ORDER_HEADERS and OE_ORDER_LINES — Accessed to associate pricing context with specific orders and order lines during pricing evaluation.
  • QP_LIST_HEADERS_B — The base table for price lists, used to retrieve the header information for the price lists referenced by the contract.
  • QP_QUALIFIERS — Stores qualifier definitions that determine when a price list or agreement applies; this is the target table for CREATE_AGREEMENT_QUALIFIER.
  • DUAL — Used for single-row SQL operations and PL/SQL evaluations.
  • PLITBLM — A standard Order Management PL/SQL table type used for passing collections of IDs or line information within the API.

Usage Notes

OE_PRICING_CONT_PVT is invoked indirectly. Its principal callers are the public package OE_PRICING_CONT_PUB and the Order Management forms OE_OE_FORM_AGREEMENT, OE_OE_FORM_CONTRACT, OE_OE_FORM_PRICE_BREAK, OE_OE_FORM_PRICE_LHEADER, and OE_OE_FORM_PRICE_LLINE. These forms rely on the package to lock, retrieve, and process pricing contract data as users maintain agreements and price lists. The package in turn references OE_PRICING_CONT_PUB, indicating a mutually reinforcing relationship between the private implementation and its public façade.

Because this is a private API, it should not be called directly from custom code; Oracle does not guarantee signature stability across patches or upgrades. Developers extending Order Management pricing or agreement functionality should use OE_PRICING_CONT_PUB, which exposes the supported interface and internally delegates to this package. When debugging pricing or agreement issues, enabling diagnostics in the private package can help trace the sequence of locking, retrieval, and qualifier creation that the public API performs.