Search Results call_mrp_atp

Overview

APPS.OE_RELATED_ITEMS_PVT is a private (PVT) PL/SQL package in Oracle Order Management, shipped under the E-Business Suite 12.1.1 and 12.2.2 releases. Its header carries the source tag $Header: OEXFRELS.pls 120.0.12020000.2 2012/07/03, confirming it belongs to the Order Management related-items file set (OEXFRELS). The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoker rather than the definer.

The business function is to support related-item and upgrade-item processing on order lines. When a user enters or defaults a related item on an order line, the application must derive ship-from organizations, resolve units of measure, apply pricing, compute availability, and populate the order request records that drive order capture. The package also exposes availability checking logic by way of the CALL_MRP_ATP procedure, which invokes the MRP Available-to-Promise engine. This is the procedure most commonly sought by developers searching on the term "call_mrp_atp," since it is the internal wrapper Oracle Order Management uses to obtain ATP/availability results for a related item without calling the public scheduling APIs directly.

Key Procedures and Functions

• GET_UPGRADE_ITEM_DETAILS — Returns item name, description, and item type for an upgrade item given its inventory item identifier.
• DEFAULTING — Applies Order Management defaulting rules for related-item attributes across a long list of inputs (organization, customer, ship-to, line and ship sets, line type, accounting and invoicing rules, dates, FOB point, price list, and others), returning the warehouse identifier and unit of measure.
• CALL_MRP_ATP — Invokes the MRP ATP engine for a related item using global organization setting, ship-from organization, item, UOM, request date, ordered quantity, customer, ship-to organization, demand class, and date type; returns available quantity, ship-from organization, available date, quantity UOM, and related outputs.
• CHECK_RESULTS_FROM_REC and INITIALIZE_MRP_RECORD — Manage the temporary MRP record used to hold scheduling results.
• GET_SHIP_FROM_ORG — Determines the appropriate ship-from organization for the request.
• COPY_HEADER_TO_REQUEST, COPY_LINE_TO_REQUEST, and COPY_ATTRIBS_TO_REQ — Populate the pricing/availability request structure from header-, line-, and attribute-level data.
• SET_PRICING_CONTROL_RECORD — Initializes the pricing control record used during the call.
• BUILD_CONTEXT_FOR_LINE and BUILD_CONTEXT_FOR_HEADER — Construct pricing attribute contexts.
• APPEND_ATTRIBUTES — Adds pricing attributes to the request.
• PRICE_ITEM and PROCESS_PRICING_ERRORS — Invoke the pricing engine for the item and handle returned errors.
• GET_ROUNDING_FACTOR, GET_PRICE_LIST_INFO, DIFFERENT_UOM, GET_CONVERSION_RATE — Support UOM comparison, price list lookup, and rounding and conversion-rate resolution.
• PRINT_TIME — Diagnostics helper for timing execution.

Tables Accessed

The package reads item and organization data from MTL_SYSTEM_ITEMS_B and its key flexfield view MTL_SYSTEM_ITEMS_KFV, and unit-of-measure data from MTL_UNITS_OF_MEASURE_TL, MTL_UOM_CONVERSIONS, and MTL_UOM_CLASS_CONVERSIONS. Availability results are staged through the APPS synonym MRP_ATP_SCHEDULE_TEMP_S. Pricing data is drawn from QP_LIST_HEADERS_B, QP_LIST_LINES, QP_PRICE_REQ_SOURCES, QP_PRICING_ATTRIBUTES, and QP_QUALIFIERS. DUAL, PLITBLM (the PL/SQL table-to-database utility), and V$TIMER are used for control and timing purposes.

Usage Notes

OE_RELATED_ITEMS_PVT is a private package and is not intended for direct customer invocation. It is called internally from Order Management related-item and upgrade-item processing, typically reached from the Sales Orders form and from the order-capture logic that defaults and validates related items on a line. The ETRM metadata records that the package is referenced by zero other packages, underscoring its role as a leaf-level implementation unit rather than a shared service entry point.

Developers researching CALL_MRP_ATP should note that this procedure is an internal wrapper around the MRP ATP schedule API and depends on caller-supplied organization, demand class, and date type context. Direct calls from custom code are unsupported, because signature behavior, records, and temporary staging tables may change between releases and are not covered by Oracle's public API commitment. Supported alternatives for availability checks are the published Order Management and scheduling APIs.