Search Results om_to_wsh_interface

Overview

OE_SHIPPING_INTEGRATION_PVT is a private PL/SQL package in the APPS schema that supports the integration between Oracle Order Management (OM) and Oracle Shipping Execution (WSH) in Oracle E-Business Suite 12.1.1 and 12.2.2. The package carries an API classification of PVT, indicating that it is an internal implementation layer and is not intended for direct invocation by external or customer-written code. Its primary business function is to manage the shipping confirmation lifecycle: processing ship-confirm transactions, updating shipping attributes on order lines, and orchestrating the interface of order data into the WSH schema so that pick, pack, and ship activities in Shipping Execution are reflected back on the originating sales order lines.

The package is tightly coupled with the public-facing OE_SHIPPING_INTEGRATION_PUB package, the bulk order processing package OE_BULK_ORDER_PVT, and the Shipping Execution group package OE_WSH_BULK_GRP. It depends on FND_API for the standard Oracle Application Object Library error and message handling conventions, and on OE_GLOBALS and OE_ORDER_PUB for global constants and public order APIs respectively.

Key Procedures and Functions

The 16 documented procedures and functions reflect the breadth of shipping activity that the package handles:

CALL_PROCESS_ORDER — entry point that coordinates processing of an order through the shipping integration flow.
VALIDATE_RELEASE_STATUS — checks whether an order line or delivery is eligible for release to the warehouse.
VALIDATE_PICK — validates pick confirmation activity before shipping proceeds.
GET_PTO_SHIPPED_QUANTITY — retrieves shipped quantities for Pick-to-Order (PTO) configurations.
UPDATE_SHIPPING_PVT and UPDATE_SHIPPING_FROM_OE — update shipping attributes and status information on order lines based on shipping execution results.
CHECK_SHIPMENT_LINE — evaluates a shipment line to determine whether it can be confirmed as shipped.
SHIP_CONFIRM_SHIP_SET — processes ship confirmation for a ship set.
SHIP_CONFIRM_PTO_KIT — processes ship confirmation for a PTO kit, which requires special handling because of its configuration structure.
SHIP_CONFIRM_STANDARD_LINE — processes ship confirmation for a standard (non-configured) order line.
PROCESS_SHIP_CONFIRM — the driver that routes a ship confirmation request to the appropriate handling logic.
PROCESS_SHIPPING_ACTIVITY — handles general shipping activity processing.
PROCESS_SMC_SHIPPING — processes shipping activity originating from the Supply Chain Management / SMC flow.
OM_TO_WSH_INTERFACE — pushes order data from Order Management into the Shipping Execution tables.
HANDLE_CONFIG_PARENT — manages the parent line of a configured item during shipping processing.
SHIP_COMPLETE — finalizes the shipping process for the affected lines.

Tables Accessed

The package reads and writes several core EBS tables through APPS synonyms. It accesses OE_ORDER_LINES and OE_ORDER_LINES_ALL to read and update order line attributes such as shipped quantity, shipping status, and line flow status. OE_DROP_SHIP_SOURCES is used for drop-ship orders in which the supplier ships directly to the customer. OE_SETS supports ship set processing. PO_LINE_LOCATIONS_ALL is referenced to resolve the purchasing side of drop-ship and back-to-back flows. WSH_DELIVERY_DETAILS holds the shipping execution detail records that are synchronized back to the order. WSH_SHIPPING_PARAMETERS supplies the shipping profile options governing default behavior. Workflow tables WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES are accessed to coordinate the order line workflow activities triggered by shipping. PLITBLM is a PL/SQL table used as an internal in-memory structure during bulk processing.

Usage Notes

Because this is a PVT package, it should not be called directly from custom code. It is normally invoked indirectly through OE_SHIPPING_INTEGRATION_PUB, OE_SHIP_CONFIRMATION_PUB, OE_BULK_ORDER_PVT, or the Shipping Execution workflow (OE_SHIPPING_WF). Typical triggers include the Ship Confirm form in Oracle Shipping Execution, the Order Management Order Organizer, and concurrent programs such as Pick Release and Ship Confirm. In 12.2.2 the behavior is functionally consistent with 12.1.1, though online patching (adop) considerations mean the package may be recompiled during patch cycles. Developers who need to extend shipping behavior should use the public package or the documented open interfaces rather than referencing OE_SHIPPING_INTEGRATION_PVT directly, since its signature is not guaranteed across patches.