Search Results update_person

Overview

PO_MASS_UPDATE_REQ_GRP is a public group-type PL/SQL package in the APPS schema that provides the application programming interface for the Purchasing mass update of person assignments on requisition and purchase order documents. Its business purpose is to allow a single administrative action to replace an existing Preparer, Approver, or Requestor on a defined range of documents, rather than requiring the user to open and re-save each document individually. This capability is typically used when an employee leaves the organization, changes responsibility, or is reassigned, and the historical documents they own must be transferred to another active person.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the calling session rather than the definer, which is the standard construct for an EBS public API that must respect the caller's security context. The header comment dates the source at version 120.2, last modified in January 2008, and identifies the object as "noship," indicating it is an internal, non-shipped API rather than a formally supported customer-facing interface.

Key Procedures and Functions

The package exposes exactly one documented procedure:

• UPDATE_PERSONS — The single entry point of the package. Its documented function is to invoke the private worker procedure PO_Mass_Update_Req_PVT.Do_Update, which performs the actual update of the Preparer, Approver, or Requestor on the affected documents, based on the input supplied from the Update_Person parameter value set.

Per the package header comments, the procedure accepts inputs that identify which person role is to be changed, the old and new person identifiers, the document type (internal requisition or purchase order), a from/to document number range, a from/to date range, and a commit interval. It returns message data in encoded format, a message count, and a standard return status of 'S' (success), 'E' (error), or 'U' (unexpected error). The parameter list is not reproduced here; the authoritative signature is defined in the package specification itself.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables referenced through APPS synonyms at the group level. The group package functions primarily as a thin wrapper that validates inputs and delegates processing to PO_Mass_Update_Req_PVT, which performs the DML. Based on the documented behavior — updating Preparer, Approver, and Requestor attributes on internal requisitions and purchase orders within given document number and date ranges — the underlying updates target the Purchasing and iProcurement requisition and document tables where these person references are stored, including PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_HEADERS_ALL, and PO_LINES_ALL. Any dependent action history or approval records tied to the changed person may also be affected through the private package logic.

Usage Notes

UPDATE_PERSONS is normally invoked from the Mass Update of Requisitions user interface, where the Update_Person parameter value set supplies the operating mode and the mass update form collects the old person, new person, document type, document number range, and date range. It can also be called from a concurrent program or from custom PL/SQL, provided the caller handles the output parameters correctly: p_return_status must be checked for 'S', and p_msg_data and p_msg_count should be interrogated to surface any errors or warnings. The procedure is not autonomous — the commit interval controls how frequently work is committed within the loop, so callers must be aware that partial completion is possible if an error occurs mid-range. Because the object is marked noship and has no other packages referencing it (referenced by 0 other packages per the metadata), customizations should depend on it only with caution and should be re-validated against the target release, since the signature is not part of the shipped, supported API surface.