Search Results pos_default_promise_date_ack

Overview

POS_ACK_PO is an Oracle E-Business Suite package body owned by the APPS schema that supports supplier acknowledgment processing for Purchasing documents. It provides the procedural logic required to record, validate, and communicate vendor responses to purchase orders, blanket releases, and related shipment schedules within Oracle Purchasing. The package operates as part of the acknowledgment and acceptance framework, bridging the transactional purchasing tables with the Oracle Workflow notification infrastructure. Its dependency footprint confirms that it interacts with purchasing acceptance records, purchase order headers, line locations, releases, vendor information, and Workflow engine objects. In Oracle EBS 12.1.1 and 12.2.2, POS_ACK_PO enables buyers and suppliers to acknowledge receipt of purchasing documents, confirm or revise promised dates, and capture acceptance details that feed downstream supply chain planning and receipt activities. The package is classified as an OTHER API type, indicating it is primarily an internal application programming unit rather than a publicly documented interface for external integration, though it remains a valid compiled object within the APPS schema.

Key Procedures and Functions

The documented API surface comprises six procedures and functions:

• ACKNOWLEDGE_PO — Serves as the principal entry point for recording a supplier or buyer acknowledgment against a purchasing document. It coordinates the validation and persistence of acknowledgment data and triggers the associated Workflow activity.
• ACKNOWLEDGE_PROMISE_DATE — Handles the acknowledgment of a promised date, allowing the supplier to confirm or adjust the date on which goods are expected, a key input to scheduling and planning.
• CREATE_HEADER_PROCESS — Establishes and initializes the Workflow header process instance associated with an acknowledgment, setting up the item context used by Oracle Workflow.
• START_HEADER_PROCESS — Commences execution of the header-level Workflow process after it has been created, driving notifications and subsequent activity transitions.
• ADD_SHIPMENT — Adds shipment-level detail to the acknowledgment, associating line locations and schedules with the response being processed.
• POS_ACK_HEADER_PROCESS — Performs the header-level processing logic that ties the acknowledgment workflow together, orchestrating the sequence of acknowledgment steps.

Tables Accessed

The package reads and writes a defined set of purchasing and Workflow tables, referenced through APPS synonyms:

• PO_HEADERS_ALL — The purchase order header, used to identify and validate the document being acknowledged.
• PO_LINE_LOCATIONS_ALL and PO_LINE_LOCATIONS_ARCHIVE_ALL — Shipment and schedule lines, including archived versions, used to resolve and update shipment details.
• PO_RELEASES_ALL — Blanket agreement releases, supported for acknowledgment processing.
• PO_ACCEPTANCES and PO_ACCEPTANCES_S — The acceptance and acknowledgment records created or updated by the package.
• PO_WF_ITEMKEY_S — Sequence generating Workflow item keys for process instances.
• WF_NOTIFICATIONS and WF_ITEM_ACTIVITY_STATUSES — Workflow notification and activity status data used to manage and monitor the acknowledgment workflow.
• FND_NEW_MESSAGES and DUAL — Supporting infrastructure for messaging and single-row queries.

Usage Notes

POS_ACK_PO is typically invoked indirectly. In Oracle Purchasing, the acknowledgment functionality accessible from the Purchase Order and Supplier Acknowledgment windows invokes this package to persist supplier responses and initiate the associated Workflow. Oracle Workflow drives the acknowledgment process, sending notifications and transitioning activities based on the procedures CREATE_HEADER_PROCESS and START_HEADER_PROCESS. Because the package relies on PO_SIGNATURE_PVT, WF_ENGINE, WF_DIRECTORY, and FND_API, it participates in the standard EBS security and messaging architecture. The ETRM metadata indicates POS_ACK_PO is not referenced by any database object but depends upon several APPS packages and is itself referenced by five other packages, confirming its role as a shared internal component. Customizations should generally avoid modifying the package directly; instead, the documented procedures should be treated as internal building blocks, and any extension should follow Oracle's supported customization guidance for the Purchasing application.