Search Results update_req_po

Overview

PO_OM_INTEGRATION_GRP is an internal integration package in the APPS schema that governs the flow of data between Oracle Purchasing (PO) and Oracle Order Management (OM) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central responsibility is the drop-ship process, in which an order management sales order line sources its supply directly from a purchase order rather than from inventory. The package translates purchasing events into the corresponding actions on the originating order or release, and conversely purges and validates the integration records that link the two modules. As a "GRP" classified package, it functions as a grouping layer: it exposes a small set of callable entry points that other PO and OM programs invoke rather than being run interactively by end users. The package maintains procedural validity in the ETRM repository and is referenced by the standard OE_ORDER_PURGE_PVT and OE_PURCHASE_RELEASE_PVT packages.

Key Procedures and Functions

The documented PL/SQL interface consists of five procedures:

• UPDATE_REQ_PO — Synchronizes requisition, purchase order, and order data when a change occurs in one of the participating documents. It propagates the updated state across the drop-ship linkage so the originating sales order reflects the current purchasing position.
• CANCEL_REQ_PO — Handles cancellation of the linked requisition or purchase order and applies the corresponding cancellation logic to the associated order or release. It ensures that cancelling supply does not leave the demand-side order in an inconsistent state.
• PURGE — Removes obsolete integration data. It is invoked to clear records that remain after order or purchase order completion, keeping the drop-ship linkage tables from accumulating stale rows.
• VALIDATE_PURGE — Performs the pre-purge validation that determines whether the referenced records are eligible for removal. It acts as the safety check that precedes PURGE so that active or incomplete drop-ship relationships are not deleted.
• GET_DROP_SHIP_DETAILS — Retrieves the drop-ship attributes for a given context, supplying the sourcing and document detail needed by the calling integration logic. It is the read-oriented counterpart to the update and cancel routines.

Tables Accessed

The package reads and writes a defined set of purchasing and order management base tables through APPS synonyms. Order-side access covers OE_ORDER_LINES_ALL and OE_DROP_SHIP_SOURCES, which hold the sales order line and the drop-ship sourcing definition. Purchasing-side access includes PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL, together with PO_HEADERS, PO_LINES, and PO_DOCUMENT_TYPES for document classification. MTL_UNITS_OF_MEASURE supplies unit-of-measure validation and conversion. PO_SESSION_GT and PO_SESSION_GT_S are session-level temporary tables used to stage processing context. The package also declares PL/SQL collections typed as PO_TBL_DATE, PO_TBL_NUMBER, PO_TBL_VARCHAR1, and PO_TBL_VARCHAR240, indicating bulk processing of dates, numbers, and variable-length character keys during mass update, cancel, or purge operations.

Usage Notes

PO_OM_INTEGRATION_GRP is a back-end integration package and is not exposed as a form-driven user transaction. It is normally invoked indirectly, through the PO and OM business flows that manage drop-ship orders. Standard Oracle code calls it from OE_ORDER_PURGE_PVT during order purge processing and from OE_PURCHASE_RELEASE_PVT during purchase release handling; because those packages depend on it, the package is automatically engaged whenever drop-ship lines are created, changed, cancelled, or purged. Custom extensions should call the documented procedures rather than modify the underlying tables directly, and any custom code must respect the dependency chain shown by the ODfC. Because it is an APPS-owned internal package, its interface is subject to change between releases, and installations should treat direct invocations as unsupported except where Oracle documentation explicitly sanctions them.