Search Results mrp_cancel_po




Overview
Explore in AI Chat

Overview

MRP_CANCEL_PO is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Materials Requirements Planning (MRP) module and provides the server-side logic required to cancel purchasing documents that the planning engine has identified as no longer needed. Within the broader planned-order and supply/demand planning flow, MRP generates recommendations for purchases; when demand changes, planned replenishment is re-evaluated, and previously created purchase orders that are no longer valid must be cancelled. MRP_CANCEL_PO encapsulates that cancellation activity so it can be executed in a controlled, batch-oriented manner rather than through manual, per-document maintenance.

The object is classified as an OTHER API in the ETRM metadata and is recorded with VALID status. Its documented dependency set includes FND_API, FND_FILE, MO_GLOBAL, PO_DOCUMENT_CONTROL_GRP, and the base table PO_HEADERS_ALL, indicating that the package relies on Oracle's standard API, file, and multi-org utilities while interacting directly with the purchasing header table. The package body is not referenced by any other database object, confirming that it operates as an entry point that is called externally rather than being embedded as a dependency in the call stack of other packages.

Key Procedures and Functions

The ETRM metadata documents a single program unit within the package: CANCEL_PO_PROGRAM. This procedure serves as the executable driver for the purchase order cancellation process. As its name implies, it constitutes the concurrent-program entry point through which the cancellation logic is initiated. It is responsible for orchestrating the identification of eligible purchase order headers and applying the cancellation action to them, wrapping the underlying operations in error handling and logging conventions consistent with the FND_API and FND_FILE dependencies recorded for the package. No parameter list is documented in the ETRM metadata, and no additional procedures or functions are listed; therefore CANCEL_PO_PROGRAM should be treated as the sole documented surface of this package body. Any invocation must supply arguments matching the actual deployed signature in the target instance.

Tables Accessed

Only one table is documented as accessed by this package: PO_HEADERS_ALL. This is the base table that stores purchasing document header information, including purchase orders, blanket purchase agreements, and contracts. Because cancellation applies to the document at the header level, PO_HEADERS_ALL is the natural target for the package's read and write activity. The package reads header records to determine which purchase orders qualify for cancellation based on the criteria established by the planning process, and it updates the relevant header rows to reflect the cancelled state. The presence of PO_DOCUMENT_CONTROL_GRP in the dependency list indicates that document-control logic is applied when performing these updates, enforcing the sequencing and authorization rules that govern changes to purchasing documents. The MO_GLOBAL dependency confirms that the package respects multi-organization security, restricting operations to the appropriate operating unit context.

Usage Notes

MRP_CANCEL_PO is typically invoked as a concurrent program from within Oracle MRP or through the standard concurrent manager, using the CANCEL_PO_PROGRAM entry point. It is most appropriate when a planner has reviewed cancellation suggestions generated by the planning engine and wishes to execute the cancellations in bulk rather than processing each purchase order manually. Because the package is not referenced by any other database object, custom code that requires this functionality must call it directly, observing the same multi-org initialization and error-handling expectations as the standard concurrent program. When invoking it from custom code, the session should first initialize the organization context through MO_GLOBAL and treat output and errors through FND_FILE conventions to remain consistent with the package's internal design. The package should be run with the privileges of the APPS schema, and any direct modification of PO_HEADERS_ALL outside its control flow risks bypassing document control and audit rules. As with all standard EBS APIs, parameters and behavior should be verified against the specific installed release and patch level before use.