Search Results check_mandatory_params

Overview

APPS.PO_DOCUMENT_UPDATE_GRP is the group (GRP-classified) API layer for the Oracle Purchasing document update process in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal responsibility is to validate and apply caller-requested modifications — together with any derived changes — to Purchase Orders, Purchase Agreements (Blanket and Contract), and Releases. It provides the public entry point through which external callers, forms, and concurrent programs submit change requests without directly manipulating the underlying Purchasing tables.

The package body header ($Header: POXGCPOB.pls 120.5) indicates this is an archived, non-shipped source file, meaning the deployed object is delivered through the standard POXGCPOB.pls path in the APPS schema. The group layer is intentionally thin: it performs standard FND_API initialization and delegates substantive validation and database write logic to PO_DOCUMENT_UPDATE_PVT. The body also honors the AFLOG_ENABLED profile option, gating debug logging through the FND logging framework, which is standard for this API family.

Key Procedures and Functions

• UPDATE_DOCUMENT — The primary public procedure. It accepts an API version and initialization flag, returns status and error structures, receives a PO_CHANGES_REC_TYPE record containing the requested modifications, and exposes control flags for submission checks, approval launching, buyer context, update source, date override, background approval, and mass update of releases. In file version 115.3 an overloaded form accepting a PO_CHANGES_REC_TYPE object was added, enabling callers to request changes to multiple lines, shipments, and distributions in a single invocation. This is the procedure that validates and applies changes and derived changes to the document.
• LAUNCH_PO_APPROVAL_WF — Initiates the Oracle Workflow approval process for a Purchasing document. It is the dedicated hand-off point between the update/validation flow and the approval routing, and is normally invoked after successful update processing when the caller requests approval.

Tables Accessed

• PO_HEADERS — The document header record being updated; header-level changes, status, and document type context are read and written here.
• PO_LINES — Line-level changes requested through PO_CHANGES_REC_TYPE are validated and applied against this table.
• PO_LINE_LOCATIONS — Shipment schedules and their attributes are updated in this table as part of the line-level change set.
• PO_RELEASES — Release documents (and releases against agreements) invoked via mass update processing are read and updated here.
• PO_DOCUMENT_TYPES_ALL_B — Supplies document type definitions used to determine valid operations and routing for the document being changed.
• MTL_GRADES — Consulted for grade validation on inventory-aware line attributes.
• FND_NEW_MESSAGES — Used by the messaging/logging infrastructure to surface error and notification text to the caller.

Usage Notes

Because it is classified as a GRP (group) API, UPDATE_DOCUMENT is the supported public interface; direct calls to the corresponding PVT package are discouraged. It is normally invoked from Purchasing forms, from concurrent programs performing mass document updates, and from custom PL/SQL that must programmatically modify a PO, agreement, or release while preserving Oracle's validation, derived-change, and approval semantics. Callers should always inspect the returned x_return_status and x_api_errors structures and must not assume success on completion of the call. The package is referenced by seven other packages, confirming its central position in the Purchasing document lifecycle, and its use is appropriate whenever a change must flow through the same validation and approval path as an interactive user edit.