Search Results po_multi_mod_pvt




Overview
Explore in AI Chat

Overview

PO_MULTI_MOD_PVT is a private PL/SQL package in the APPS schema that supports Oracle Purchasing's multi-modification feature set in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A "multi-modification" (multi-mod) allows a buyer to bundle several related changes—price, quantity, promise date, or other line attributes—into a single modification request, which is then routed through the appropriate approval path. The package carries the PVT suffix, indicating that it is an internal, private-layer API rather than a public interface. It is invoked by Oracle's own Purchasing code, principally PO_CLOSEOUT_PVT and the package's own subordinate routines, and is not intended as a published integration point for external callers.

Functionally, PO_MULTI_MOD_PVT orchestrates the lifecycle of a multi-mod request: assembling the modification document, submitting it for approval, and cleaning up associated records when a request is withdrawn, deleted, or otherwise terminated. The presence of routine names such as START_MOD_APPROVAL and REMOVE_MULTI_MOD_REQUEST confirms that the package spans both the creation/approval side and the removal side of the multi-mod process.

Key Procedures and Functions

  • START_MOD_APPROVAL — Initiates the approval workflow for a multi-modification request. It is the entry point that moves a prepared modification from draft state into the approval process, working in conjunction with the AME-based approval records stored by the package (see PO_AME_APPROVALS_S below).
  • CREATE_MODIFICATION — Creates the modification document itself. This routine establishes the header-level change record for the multi-mod and is responsible for persisting the document data on which subsequent approval and cleanup logic operate.
  • REMOVE_MMOD_DOC_DATA — Removes multi-modification document data. It is used when a modification document must be dismantled or its transient rows purged, for example after the modification completes or is abandoned.
  • REMOVE_MULTI_MOD_REQUEST — Removes an entire multi-modification request, covering the broader set of rows that constitute the request rather than the document data alone. This supports withdrawal or cancellation scenarios.
  • REMOVE_FROM_ASL — Removes the multi-modification's association from the Approved Supplier List. Multi-mod changes can affect supplier sourcing, so this routine cleans up the ASL linkage (PO_ASL_DOCUMENTS) when the modification is removed.

These five routines are the documented public surface of the package. Parameter lists are not published in the ETRM metadata and should be obtained from the package specification in the target instance before any direct invocation.

Tables Accessed

Usage Notes

PO_MULTI_MOD_PVT is an internal package. It is referenced by PO_CLOSEOUT_PVT and by itself, which confirms its role as a supporting utility within the Purchasing private layer rather than a documented public API. In normal operation it is invoked indirectly through the Purchasing forms and the multi-modification concurrent programs when a buyer prepares, approves, or withdraws a multi-mod request. Custom code should not call this package directly; where modification control is required, the supported approach is to drive the underlying Purchasing forms or use the officially published Purchasing open interfaces. Any direct dependence on PO_MULTI_MOD_PVT should be treated as an unsupported customization, since its signature and internals are subject to change across patch levels and releases.