Search Results pass_modifiers_to_backend

Overview

OE_OE_PRICING_AVAILABILITY is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. As its name implies, it encapsulates the pricing and availability (ATP) processing logic used by the Oracle Order Management (OM) module. It acts as an internal service layer that supports the public Order Management APIs and validation routines, most notably OE_ORDER_PUB and OE_VALIDATE_LINE. Its primary business function is to evaluate whether an order line can be priced according to the applicable price list, apply or remove pricing modifiers and manual adjustments, and confirm product availability against available-to-promise schedules before the order line is committed. The package is classified as an "OTHER" API in the ETRM repository, meaning it is not a formally published public API but rather an internal utility invoked by other OM packages and forms. Because it consolidates pricing and ATP logic in one place, it enables consistent behavior across order entry, order import, and upgrade flows.

Key Procedures and Functions

The ETRM documentation lists 58 procedures and functions. Representative examples include:

• PASS_MODIFIERS_TO_BACKEND — forwards qualifying pricing modifiers to the pricing engine for application to the order line.
• ENFORCE_PRICE_LIST — ensures that a valid price list governs the transaction line during pricing.
• DELETE_MANUAL_MODIFIERS / DELETE_APPLIED_MANUAL_ADJ — remove manually entered modifiers and previously applied manual adjustments from a line.
• INSERT_MANUAL_ADJUSTMENT — inserts a user-defined price adjustment onto the line.
• CALL_MRP_ATP — invokes the MRP available-to-promise engine to determine supply availability for the requested item and date.
• GET_ITEM_NAME / GET_UPGRADE_ITEM_DETAILS / PASS_UPGRADE_INFORMATION — retrieve item descriptions and manage upgrade-related item attributes, supporting item substitution and upgrade scenarios.
• GET_OID_INFORMATION — returns order information context needed for downstream processing.
• GET_TERMS_DETAILS / GET_COUPON_DETAILS — obtain payment-term and coupon-related pricing data.
• DEFAULTING — applies defaulting rules to populate missing attribute values on the pricing/availability call.
• Get-value functions such as GET_ORDER_TYPE, GET_SOLD_TO_ORG, GET_SHIP_TO_ORG, GET_INVOICE_TO_ORG, GET_CURRENCY_NAME, GET_DEMAND_CLASS, GET_AGREEMENT_NAME — resolve key order attributes required for correct pricing and availability evaluation.

In accordance with ETRM conventions, parameter lists are not reproduced here; only the documented purposes are described.

Tables Accessed

The package reads and writes data through APPS synonyms. Key tables include:

• OE_ORDER_LINES_ALL — the core order line table; the package updates pricing, modifier, and availability attributes on the line.
• QP_INT_LDETS_T and QP_INT_LINES_T — pricing engine interface tables used to pass line and modifier details to and from Oracle Advanced Pricing.
• MRP_ATP_SCHEDULE_TEMP and MRP_ATP_SCHEDULE_TEMP_S — temporary ATP schedule tables populated by the MRP ATP engine for availability checks.
• MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV — item master and key-flex views for item validation and display name resolution.
• MTL_UNITS_OF_MEASURE_TL, MTL_UOM_CONVERSIONS, MTL_UOM_CLASS_CONVERSIONS — unit of measure translations and conversion factors needed to convert quantities between pricing and inventory UOMs.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — customer account and party information for sold-to, ship-to, and invoice-to context.
• FND_ID_FLEX_STRUCTURES and FND_LANGUAGES — key flexfield structure definitions and language settings used for item and descriptive flexfield handling and multi-language support.

Usage Notes

OE_OE_PRICING_AVAILABILITY is invoked internally rather than called directly by end users. It is referenced by OE_ORDER_PUB, the primary public Order Management API, and by OE_VALIDATE_LINE. Consequently, it executes automatically during order entry (via the Order Management forms), during Order Import (OE_ORDER_PUB calls from the import concurrent program), and during order upgrade processing. Customizations and extensions that call OE_ORDER_PUB indirectly trigger this package. Because it is an internal, undocumented-public package, direct invocation by custom code is discouraged; Oracle recommends using the published OE_ORDER_PUB API, which encapsulates calls to this package. Deployments in 12.1.1 and 12.2.2 rely on the same underlying pricing engine and MRP ATP integration, so behavior is consistent across both releases, though schema and synonym resolution must be validated after upgrades. Any modification should be limited to supported extension points to avoid violating Oracle's support policy.