Search Results reschedule_po

Overview

MRP_RESCHEDULE_PO is an Oracle Applications (APPS) PL/SQL package that supports the rescheduling of purchase order (PO) supply records in response to changes in planned need-by dates generated by Oracle's material planning engine (MRP/MPS). The package header carries the version identifier MRPRSPOS.pls 120.0.12010000.2, dated 2008/12/12, which corresponds to the R12 code line and is therefore applicable to both Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Within the planning cycle, rescheduling messages recommend moving existing supply (purchase orders, requisitions, planned orders) forward or backward to align with demand. This package provides the programmatic and concurrent-program entry points through which the planning application applies those reschedule recommendations to the actual purchase order documents in Oracle Purchasing.

Key Procedures and Functions

The package exposes four documented program units:

• RESCHEDULE_PO_PROGRAM — A concurrent-program style procedure with the standard concurrent manager signature (errbuf and retcode OUT parameters) plus parameters describing old and new need-by dates, the purchase order header and line identifiers, vendor purchase order number, and quantity. It is the batch-apply entry point that processes a single reschedule instruction against a PO shipment or distribution.
• RESCHEDULE_PO — A boolean-returning function that operates on sets of reschedule data supplied through PL/SQL collection types (po_tbl_date, po_tbl_number, po_tbl_varchar30). Its parameters carry arrays of old need-by dates, new need-by dates, PO header IDs, PO line IDs, shipment numbers, estimated pickup dates, and ship methods, allowing a batch of reschedule instructions to be applied in a single invocation.
• GET_REQUEST_STATUS — A documented accessor that reports the status of a reschedule request, enabling callers to determine processing outcome before proceeding with dependent planning logic.
• SET_RESULT — A documented helper that records or returns the result of the reschedule operation, supporting the status reporting performed by GET_REQUEST_STATUS.

Parameter lists are not reproduced here where the metadata does not fully define them; callers should consult the package specification for exact signatures.

Tables Accessed

The package reads and writes the core Oracle Purchasing tables through APPS synonyms:

• PO_HEADERS_ALL — the parent purchase order record; used to identify the document being rescheduled.
• PO_LINES_ALL — the PO line detail; used to locate the line affected by the new need-by date.
• PO_LINE_LOCATIONS_ALL — the shipment and distribution schedules that carry need-by and promised dates; this is where reschedule date updates are applied.
• MRP_AP_APPS_INSTANCES_ALL — the multi-instance registry table used by advanced planning to resolve instance context.
• PLITBLM — the standard Oracle Application Object Library message/error table, used to surface errors raised during processing.

Usage Notes

MRP_RESCHEDULE_PO is invoked primarily from the Oracle Planning and Purchasing modules during execution of reschedule messages — either from the planning workbench interface or from concurrent programs that apply planning recommendations. Because RESCHEDULE_PO_PROGRAM follows the concurrent-manager signature, it can be registered and submitted as a standalone concurrent program; the RESCHEDULE_PO function supports custom code that needs to apply reschedule changes programmatically across multiple shipments. It is commonly wired into custom interfaces that synchronize external supply schedules with EBS purchase orders. The package is not documented as being referenced by other packaged APIs, so impacts are confined to direct callers. As with all EBS supply-update APIs, callers should respect open interface conventions, commit after success, and handle the returned status via GET_REQUEST_STATUS.