Search Results insert_drop_ship_source

Overview

OE_PURCHASE_RELEASE_PVT is a private PL/SQL package in the APPS schema that supports the purchase release and drop-shipment processing performed by Oracle Order Management. In Oracle E-Business Suite 12.1.1 and 12.2.2, drop-ship orders and back-to-back supply arrangements require Order Management to communicate demand to Oracle Purchasing and to manage the relationship between a sales order line and its supplier source. This package encapsulates that logic, providing the internal implementation behind purchase release creation, drop-ship source maintenance, and the transmission of order information into the purchasing requisition interface.

The package is classified as a PVT (private) API. It is not intended as a public integration interface; it is invoked internally by other Order Management components. Its documented dependencies include FND_API, which supplies the standard EBS API error-handling and message framework, and OE_ORDER_PUB, which exposes the public order-processing APIs used to read and update order data. The package is referenced by OE_DELAYED_REQUESTS_PVT, OE_OEOL_SCH, and OE_PURCHASE_RELEASE_PVT itself, confirming that it operates as a supporting utility within the Order Management scheduling and delayed-request infrastructure.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within this package:

• PURCHASE_RELEASE — The primary routine that initiates the purchase release process for eligible order lines, coordinating the creation of purchasing demand from sales order supply requirements.
• INSERT_INTO_PO_REQ_INTERFACE — Inserts the relevant order line details into the Purchasing requisition interface tables so that Oracle Purchasing can subsequently import the demand and generate requisitions.
• INSERT_DROP_SHIP_SOURCE — Creates or populates drop-ship source records, establishing the supplier linkage for drop-ship order lines.
• ASSOCIATE_ADDRESS — Associates the appropriate address information, aligning customer and supplier site data required for drop-ship and purchase release processing.
• GET_ELIGIBLE_LINES — Identifies and returns the order lines that qualify for purchase release processing, applying the business rules that determine eligibility.
• PROCESS_DROPSHIP_CMS_REQUESTS — Processes drop-ship requests originating from the order capture or order management flow, handling the coordination required for drop-ship fulfillment.

Parameter lists are not reproduced in the available metadata and should be confirmed against the package specification in the target environment.

Tables Accessed

The package reads and writes Oracle Order Management and Oracle Purchasing tables through APPS synonyms. Order data is handled via OE_ORDER_HEADERS, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL, which provide header and line context for the lines under processing. Drop-ship configuration is managed through OE_DROP_SHIP_SOURCES and OE_DROP_SHIP_SOURCE_S, where source definitions and their translations or flexfield-related records reside.

Item and revision validation relies on MTL_SYSTEM_ITEMS, MTL_ITEM_REVISIONS, and MTL_PARAMETERS. Customer and address information is resolved through HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, and HZ_PARTY_SITES, ensuring that the correct ship-to and customer site details are associated with the drop-ship source. PO_LOCATION_ASSOCIATIONS links purchasing locations to the relevant address or site configuration, and FND_USER is consulted for user context. These reads support eligibility determination, address association, and the population of the requisition interface.

Usage Notes

OE_PURCHASE_RELEASE_PVT is an internal package and is not documented as a public API. It is typically invoked indirectly through Order Management processing rather than directly from custom code. The principal callers are OE_DELAYED_REQUESTS_PVT, which manages deferred request execution, and OE_OEOL_SCH, which handles order line scheduling. In practice, this package is triggered when drop-ship or back-to-back order lines are processed, when purchase release demand must be forwarded to Purchasing, or when drop-ship source and address information must be maintained.

Because the package depends on FND_API, it participates in the standard EBS concurrent and online processing model, including message stacking and error propagation. Customizations should avoid calling the package directly; instead, they should use the supported public APIs in OE_ORDER_PUB or the documented concurrent programs that drive drop-ship and purchase release processing. Any extension work should account for the fact that the package is referenced by scheduling and delayed-request components, so changes to its behavior can affect order scheduling and purchasing integration.