Search Results purchase_release

Overview

OE_PURCHASE_RELEASE_PVT is an internal (private) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It provides the core implementation logic that supports drop-shipment and back-to-back purchase release processing within the Oracle Order Management (OM) and Oracle Purchasing (PO) integration flow. In a drop-ship model, the selling entity does not hold inventory; instead the order line is fulfilled directly by a supplier, and a requisition and subsequent purchase order must be generated automatically. This package embodies the release of that demand to Purchasing.

Because the object is classified as a PVT (private) package, it is not part of the supported public API surface. Its procedures are invoked internally by other OM packages—most notably the public OE_ORDER_PUB and OE_PURCHASE_RELEASE_PUB layers—and by concurrent programs that build and submit purchasing documents. The user search term oe_drop_ship_source_s corresponds to the sequence that this package directly references to generate primary keys for the OE_DROP_SHIP_SOURCES table.

Key Procedures and Functions

The documented package exposes six procedures:

• PURCHASE_RELEASE — The main driver that releases eligible order line demand into the purchasing pipeline, coordinating requisition creation and supplier sourcing.
• INSERT_INTO_PO_REQ_INTERFACE — Populates PO_REQUISITIONS_INTERFACE_ALL with the requisition rows derived from order lines destined for drop-ship or back-to-back supply.
• INSERT_DROP_SHIP_SOURCE — Creates the drop-ship sourcing record, drawing its key from the OE_DROP_SHIP_SOURCE_S sequence.
• ASSOCIATE_ADDRESS — Links ship-to and supplier address information, using the HZ location and site tables, so the purchase document carries the correct delivery address.
• GET_ELIGIBLE_LINES — Identifies order lines eligible for purchase release based on item, source, and configuration criteria.
• PROCESS_DROPSHIP_CMS_REQUESTS — Handles drop-ship change management (CMS) request processing for already-released lines.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables. Order data is sourced from OE_ORDER_HEADERS, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL. Sourcing and drop-ship configuration is stored in OE_DROP_SHIP_SOURCES and OE_DROP_SHIP_SOURCE_S. Item and revision validation uses MTL_SYSTEM_ITEMS, MTL_ITEM_REVISIONS, MTL_PARAMETERS, and INV_ORGANIZATION_INFO_V. Requisition output is written to PO_REQUISITIONS_INTERFACE_ALL, with PO_LOCATION_ASSOCIATIONS supporting location resolution. Address and party information is drawn from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and FND_USER.

Usage Notes

OE_PURCHASE_RELEASE_PVT is invoked indirectly. Standard OM drop-ship flows call OE_ORDER_PUB, which delegates to this private package during order booking and line processing. The package is also driven by concurrent programs that submit requisition interface records. It is not referenced by any database object outside the OM/PO package stack, confirming its role as an internal implementation unit. Customizations should target the public OE_ORDER_PUB and OE_PURCHASE_RELEASE_PUB interfaces rather than this package directly, since its signature and behavior are not guaranteed across patches.