Search Results update_document

Overview

APPS.PO_DOCUMENT_UPDATE_GRP is the public group (GRP) package in Oracle Purchasing that exposes the supported application programming interface for modifying and re-approving existing purchasing documents. Its central responsibility is to validate and apply requested changes, together with any derived changes, to a Purchase Order, Purchase Agreement, or Release. Because it is a group package rather than a private package, it defines the entry points that external callers and Oracle E-Business Suite modules are expected to invoke, while delegating the substantive processing logic to the private package PO_DOCUMENT_UPDATE_PVT.

The package header carries the signature marker for the PO_CHANGE_API_FPJ feature and the version string $Header: POXGCPOS.pls 120.2.12020000.2 2013/02/10, confirming its applicability to the 12.1.1 and 12.2.2 code lines. A package-level variable, g_process_param_chge_only, initialized to 'N' and annotated with the INVCONV R12 marker, allows callers to restrict processing to parameter changes only. The package operates with AUTHID CURRENT_USER, so privilege resolution occurs against the invoking schema.

Key Procedures and Functions

• UPDATE_DOCUMENT — The primary interface for document modification. It validates and applies requested changes and derived changes to a Purchase Order, Purchase Agreement, or Release. The header comments note that, as of file version 115.4, an overloaded form of update_document accepts changes as a PO_CHANGES_REC_TYPE object, enabling a single call to request changes across multiple lines, shipments, and distributions simultaneously. Documented parameters include p_api_version, p_init_msg_list, x_return_status, p_changes, p_run_submission_checks, p_launch_approvals_flag, p_buyer_id, p_update_source, p_override_date, x_api_errors, p_approval_background_flag, p_mass_update_releases, and p_req_chg_initiator. For behavioral detail, the comments direct the reader to PO_DOCUMENT_UPDATE_PVT.update_document.
• LAUNCH_PO_APPROVAL_WF — Launches the Document Approval workflow for the given document, allowing the purchasing approval process to be initiated programmatically after changes are applied. Its implementation detail is documented in PO_DOCUMENT_UPDATE_PVT.launch_po_approval_wf.

The ETRM metadata records three documented program units in total, with UPDATE_DOCUMENT and LAUNCH_PO_APPROVAL_WF named explicitly.

Tables Accessed

Through APPS synonyms, the package reads and writes the core purchasing document tables. PO_HEADERS, PO_LINES, and PO_LINE_LOCATIONS hold the order, agreement, or release header, line, and shipment/schedule data that changes are applied to. PO_RELEASES supports release-level updates and, given the p_mass_update_releases parameter, blanket agreement release mass maintenance. PO_DOCUMENT_TYPES_ALL_B supplies document type definitions that govern validation rules. FND_NEW_MESSAGES supports messaging and notification behavior, and MTL_GRADES is referenced for item grade attributes.

Usage Notes

PO_DOCUMENT_UPDATE_GRP is typically invoked from the Purchasing forms when a user modifies a document, from concurrent programs such as mass update of releases, and from custom PL/SQL integrations that must change purchasing documents under the same validation and approval rules enforced by the application. Because the package raises errors through x_return_status and x_api_errors rather than by exception alone, callers must initialize the message list, check the return status after every call, and inspect the error record for validation failures. The metadata shows the package is referenced by seven other packages, indicating its role as a shared, dependency-bearing API within the purchasing module. Custom code should always call this group package rather than the underlying private package.