Search Results qp_price_formulas

Overview

QP_JAVA_ENGINE_CACHE_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle Advanced Pricing Java pricing engine cache within Oracle E-Business Suite releases 12.1.1 and 12.2.2. The package manages the server-side cache structures used by the Java Engine to evaluate pricing attributes, qualifiers, modifiers, and price formulas without repeatedly querying the base pricing tables. Its scope covers cache synchronization with pricing setup data, controlled warm-up of cache content, runtime cache administration, and collection of cache performance statistics. Because the package is classified as PVT, it is not part of the public API surface; it is invoked internally by the pricing engine infrastructure and by the associated utility package QP_JAVA_ENGINE_UTIL_PUB. The package depends on a broad set of Oracle Pricing base objects, which confirms its role as a repository-level access layer for the Java cache rather than a business-facing API.

Key Procedures and Functions

The package body exposes four documented programs:

• WARM_UP — Preloads or refreshes Java engine cache content so that subsequent pricing calls do not incur first-use latency. It is typically run after pricing setup changes or as part of environment preparation.
• SYNCHRONIZE — Reconciles the in-memory or persisted cache with the underlying pricing definitions, ensuring the Java engine operates against current setup data. This is the principal mechanism for propagating pricing changes into the cache.
• UPDATE_CACHE_STATS — Records or refreshes cache statistics used for monitoring and diagnostics, drawing on the QP_CACHE_STATS structure.
• MANAGE — Provides administrative control over cache behavior, such as initialization, cleanup, or size management, supported by the QP_CACHE_DO_SIZES configuration table.

The package body also references internal units and the QP_JAVA_ENGINE_UTIL_PUB package, indicating that these entry points coordinate with shared cache utilities rather than operating in isolation. No parameter lists are documented in the ETRM metadata; the descriptions above reflect the documented program purposes only.

Tables Accessed

The package reads and maintains data across several categories of pricing and reference tables, accessed through APPS synonyms:

• Cache control: QP_CACHE_DO_SIZES and QP_CACHE_STATS govern cache sizing and recorded statistics.
• Price formulas: QP_PRICE_FORMULAS and QP_PRICE_FORMULA_LINES supply formula definitions and their component lines, directly relevant to searches on "qp_price_formulas."
• Lists and modifiers: QP_LIST_HEADERS_B, QP_LIST_LINES, QP_RLTD_MODIFIERS, QP_QUALIFIERS, and QP_PATTERNS/QP_PATTERN_PHASES define price lists, qualifiers, and modifier relationships.
• Pricing structure: QP_PRC_CONTEXTS_B, QP_PRICING_ATTRIBUTES, QP_PRICING_PHASES, QP_EVENT_PHASES, QP_ATTRIBUTE_GROUPS, and QP_SEGMENTS_B define contexts, attributes, phases, and segment structures.
• Currency and UOM: QP_CURRENCY_DETAILS, QP_CURRENCY_LISTS_B, MTL_UOM_CONVERSIONS, MTL_UOM_CLASS_CONVERSIONS, OKX_UNITS_OF_MEASURE_V, and OKC_TIME_CODE_UNITS_B support currency and unit-of-measure conversion during price evaluation.
• Profile options: FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES provide runtime configuration values that influence cache behavior.

The package also depends on FND_API, FND_FILE, FND_GLOBAL, FND_MESSAGE, OE_DEBUG_PUB, DBMS_LOCK, PLITBLM, and UTL_HTTP, confirming its integration with EBS logging, debugging, locking, and messaging infrastructure.

Usage Notes

QP_JAVA_ENGINE_CACHE_PVT is not intended to be called directly from custom forms or reports. It is invoked internally during Java pricing engine startup, cache initialization, and synchronization events. In practice it is triggered by the pricing engine infrastructure and by QP_JAVA_ENGINE_UTIL_PUB, which orchestrates cache operations on behalf of the pricing application. Administrators may indirectly influence it through profile options and cache administration concurrent processes that warm or synchronize the Java engine cache. The package is referenced by one other package, indicating a contained dependency footprint consistent with its private classification. Because it is a PVT package, direct invocation from custom code is discouraged; the supported public pricing APIs should be used instead, and any reliance on this object should be treated as internal behavior subject to change between releases.