Search Results pass_values_to_backend

Overview

The APPS.OE_OE_AVAILABILITY package is a PL/SQL component within the Oracle E-Business Suite Order Management (OE) module. Its primary business function is to support Available-to-Promise (ATP) availability inquiries and integrated pricing calculations for sales order lines. The package serves as a bridge between Order Management and two critical subsystems: Oracle Advanced Supply Chain Planning (ASCP/ATP) and Oracle Advanced Pricing (QP). It queries ATP schedules to determine available quantities, applies pricing rules, and manages the transfer of request and response records between the Order Management forms layer and the backend availability and pricing engines. The package carries a classification of OTHER, indicating that it is not a formally published public API but rather an internal supporting package invoked by Order Management transactions and related UI components. Its status is VALID, confirming that it compiles cleanly against the referenced dependencies in the documented environment. Because it is referenced by zero other packages, its role is primarily as a leaf-level utility called directly by forms or concurrent processes rather than by other PL/SQL routines.

Key Procedures and Functions

The package exposes 35 documented procedures and functions, which fall into several functional clusters.

• ATP and availability routines: CALL_MRP_ATP, CHECK_RESULTS_FROM_REC, INITIALIZE_MRP_RECORD, QUERY_QTY_TREE, and GET_SHIP_FROM_ORG handle interaction with the ATP scheduling engine. CALL_MRP_ATP submits availability requests to MRP_ATP_PUB, INITIALIZE_MRP_RECORD prepares the request structure, CHECK_RESULTS_FROM_REC interprets returned records, QUERY_QTY_TREE determines quantity availability across the sourcing hierarchy, and GET_SHIP_FROM_ORG resolves the appropriate ship-from organization.
• Request copy and context building: COPY_HEADER_TO_REQUEST, COPY_LINE_TO_REQUEST, BUILD_CONTEXT_FOR_LINE, and BUILD_CONTEXT_FOR_HEADER populate ATP request structures from order header and line data, translating Order Management fields into the format expected by the availability engine.
• Attribute handling: COPY_ATTRIBS_TO_REQ, APPEND_ATTR_TO_TTABLES, APPEND_ATTRIBUTES, RESET_ALL_TBLS, and DEFAULTING manage the flexible attribute and descriptive flexfield values attached to requests, including defaulting logic and temporary table population.
• Pricing routines: SET_PRICING_CONTROL_RECORD, PRICE_ITEM, PASS_VALUES_TO_BACKEND, and PROCESS_PRICING_ERRORS integrate with Advanced Pricing, invoking QP_ATTR_MAPPING_PUB and QP_PREQ_GRP to price order lines and handle errors returned from the pricing engine.
• Result management: POPULATE_TEMP_TABLE and POPULATE_RESULTS move ATP and pricing output into temporary and result tables for consumption by the calling form.

Tables Accessed

The package reads and writes several Order Management and planning tables via APPS synonyms. MRP_ATP_SCHEDULE_TEMP and MRP_ATP_SCHEDULE_TEMP_S are the primary ATP staging tables where availability schedules and results are held. MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV supply item master attributes required for eligibility checks and descriptive defaults. MTL_UNITS_OF_MEASURE_TL, MTL_UOM_CLASS_CONVERSIONS, and MTL_UOM_CONVERSIONS provide unit of measure and conversion data needed to express availability in the correct selling UOM. Pricing integration relies on QP_LIST_HEADERS_B, QP_LIST_LINES, QP_PRICE_REQ_SOURCES, QP_PRICING_ATTRIBUTES, and QP_QUALIFIERS, which supply price lists, modifiers, and qualifier rules. DUAL is used for single-row queries, and PLITBLM supports PL/SQL table operations internal to the package.

Usage Notes

OE_OE_AVAILABILITY is typically invoked from the Oracle Order Management Sales Orders form (OEXOEORD) when a user requests availability or ATP information for a line, and from related pricing flows that require integrated availability checking. It may also be called by custom PL/SQL extensions or concurrent programs that perform bulk availability inquiries or pricing simulations. Because the package is classified as OTHER rather than as a published API, Oracle does not guarantee backward compatibility of its interfaces between releases. Developers should not call its internal procedures directly unless following Oracle's documented integration guidance; instead, supported ATP and pricing APIs such as MRP_ATP_PUB and QP_ATTR_MAPPING_PUB should be used where possible. When debugging availability or pricing issues in Order Management, tracing calls into this package is often necessary to understand how request records are built and how results are interpreted.