Results for “po_acknowledge_po_grp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_ACKNOWLEDGE_PO_GRP is a Group (GRP) type PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It serves as the public-facing group layer for the supplier purchase order acknowledgement process, in which a supplier confirms, rejects, or proposes changes to individual purchase order shipments. The group package encapsulates the workflow-level and multi-shipment coordination logic that surrounds the lower-level validation and DML routines, exposing a coarse-grained API surface rather than raw row-level operations.

Per the ETRM metadata the package body is VALID and is classified as an API group. It is not referenced by any database object, but it references the FND_API, FND_LOG, FND_MSG_PUB, and FND_PROFILE foundation packages, the PO_ACKNOWLEDGE_PO_PVT private package, and itself. The PL/SQL body therefore acts as an orchestration layer: it manages the API message stack, performs profile-option lookups, logs diagnostics through FND_LOG, and delegates detailed validation and persistence work to PO_ACKNOWLEDGE_PO_PVT.

Key Procedures and Functions

Six documented procedures and functions make up the public interface of the package:

• GET_PO_STATUS_CODE — Returns the acknowledgement status code associated with a purchase order or its acknowledgement context, allowing callers to evaluate the current acknowledgement state without directly querying the base tables.
• GET_SHIPMENT_ACK_CHANGE_STATUS — Retrieves the change status for a shipment-level acknowledgement, indicating whether an acknowledgement introduced a change that requires buyer attention or re-approval.
• ACKNOWLEDGE_SHIPMENT — The primary operative routine. It applies a supplier acknowledgement at the shipment level, coordinating validation, message handling, and delegation to PO_ACKNOWLEDGE_PO_PVT for the underlying record updates.
• CARRY_OVER_ACKNOWLEDGEMENT — Propagates or preserves an existing acknowledgement when a purchase order or shipment is revised, ensuring acknowledgement history is not lost across document revisions.
• ALL_SHIPMENTS_RESPONDED — Evaluates whether every shipment on the order has received a supplier response, typically used to determine when the header-level acknowledgement can be considered complete.
• SET_HEADER_ACKNOWLEDGEMENT — Establishes the header-level acknowledgement indicator once the condition tested by ALL_SHIPMENTS_RESPONDED has been satisfied, rolling shipment responses up to the order header.

Tables Accessed

The ETRM record for this package body documents no direct table references through APPS synonyms. All data access is performed indirectly through the PO_ACKNOWLEDGE_PO_PVT private package, which owns the SQL statements that read and write the purchase order acknowledgement tables (including the PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_ACKNOWLEDGEMENTS subject areas). This separation keeps the group layer free of embedded SQL and confines DML to the private layer, which is the standard Oracle EBS API architecture. Because no direct table dependencies are documented, the package's coupling to the data model is expressed entirely through PO_ACKNOWLEDGE_PO_PVT; the group body's own dependencies are confined to FND foundation utilities and profile lookups.

Usage Notes

PO_ACKNOWLEDGE_PO_GRP is referenced by four other packages, indicating it is consumed within the purchasing module rather than being a terminal entry point. It is typically invoked from the supplier-facing acknowledgement pages and from Oracle iSupplier Portal flows, and may be called by concurrent or workflow-driven processes that process acknowledgements in bulk. In custom extensions, the package should be called in preference to direct inserts or updates against the acknowledgement tables, since it enforces the message-stack discipline of FND_API and honors FND_PROFILE-based behavior. Callers should initialize the FND_API message stack and check the returned API status before committing, and should not expect the group routines to perform their own commits.