Search Results warm_up

Overview

QP_JAVA_ENGINE_CACHE_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Advanced Pricing (QP) module's Java-based pricing engine infrastructure. The pricing engine evaluates complex pricing rules, qualifiers, modifiers, and formulas against transaction lines in Order Management, Order Capture, and related modules. Because evaluating pricing patterns on every transaction is computationally expensive, the pricing engine relies on a set of runtime caches — pattern caches, attribute group caches, and currency detail caches — to accelerate rule resolution.

The QP_JAVA_ENGINE_CACHE_PVT package is the private control layer responsible for managing, warming, and synchronizing these caches between the database and the middle-tier Java pricing engine. Its PVT classification indicates that it is an internal implementation package not intended as a public API; it is invoked by other pricing packages rather than directly by customers. It depends on SYS.STANDARD and is referenced by QP_JPE_CTRL_PVT, its primary controlling peer, as well as self-referencing.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions. No parameter lists are documented, so only purposes are described.

• UPDATE_CACHE_STATS — Records and refreshes statistics describing the state and utilization of the pricing engine caches. This supports monitoring and diagnostics of engine performance.
• WARM_UP — Pre-populates the pricing engine caches with frequently accessed pricing definitions so that the first user transaction does not incur cold-cache latency. Typically run during system start-up or after cache invalidation.
• SYNCHRONIZE — Aligns the cached data held by the Java pricing engine with the current database state, refreshing entries that have changed since the last load.
• MANAGE — Provides the coordinating entry point that orchestrates cache lifecycle operations, including initialization, invalidation, and maintenance tasks.

Tables Accessed

The package references a substantial set of pricing and setup tables through APPS synonyms. Pricing definition sources include QP_LIST_HEADERS_B, QP_LIST_LINES, QP_PATTERNS, QP_PATTERN_PHASES, QP_EVENT_PHASES, QP_ATTRIBUTE_GROUPS, QP_CURRENCY_LISTS_B, and QP_CURRENCY_DETAILS — these define price lists, modifiers, qualifiers, pattern structures, and currency handling that the engine evaluates. Cache management and monitoring tables include QP_CACHE_STATS and QP_CACHE_DO_SIZES, which hold statistics and configurable cache sizing for the engine's data objects.

Foundation tables supply contextual and conversion data: FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES provide profile-driven configuration, and MTL_UOM_CONVERSIONS and MTL_UOM_CLASS_CONVERSIONS supply unit-of-measure conversion factors used in pricing calculations. OKC_TIME_CODE_UNITS_B supports time-based unit definitions used in complex pricing. These tables are predominantly read during warm-up and synchronization, with QP_CACHE_STATS and QP_CACHE_DO_SIZES being written by the statistics and sizing operations.

Usage Notes

Because QP_JAVA_ENGINE_CACHE_PVT is a private package, it is not designed to be called directly from custom code. Its public-facing control counterpart, QP_JPE_CTRL_PVT, invokes it to manage the engine's cache lifecycle. Typical invocation occurs during concurrent program runs such as pricing engine cache warm-up or refresh processes, during system startup, and after migrations or bulk pricing definition changes that invalidate cached data. Administrators seeking to refresh the pricing engine cache should use the documented concurrent programs or QP_JPE_CTRL_PVT rather than this package. Customizations requiring direct cache manipulation should be developed cautiously, as private packages may change between releases; the content above reflects the ETRM 12.2.2 metadata and applies equally to 12.1.1 where the pricing engine architecture is shared.