Oracle Order Management - Interface Trip Stop Process

Oracle Order Management - Interface Trip Stop Process

Interface Trip Stop is one of the main interface program which can be triggered at the time of ship confirm or later as Interface Trip stop - SRS concurrent request.

In Oracle Order to Cash Cycle the processing of the sales order after Shipping Execution ships the delivery, shipping module needs to interface the information back to Oracle Order Management and Oracle Inventory Management Modules also. This is done via the Interface Trips Stop Concurrent Program. 

Order Management Interface occurs first, then the Inventory Interface occurs

Interfaces can be run individually for Order Management and Inventory.  However, the system will not allow to run Inventory Interface until Order Management has completed successfully

Feature of Interface Trip Stop Process is to:
1. Update the Order Management Data (oe_order_lines_all)
2. Trigger the Inventory Interface (to update the Inventory tables)
Both these parts are executed simultaneously.

But the Inventory Interface will be trigger only if the first part, that is update to Order Management has successfully completed and flag oe_interfaced_flag = ‘Y’ on the table “wsh_delivery_details”. If value of this flag is N/P then Inventory Interface will never be triggered and even if tried manually to submit the Inventory Interface from SRS, delivery detail with oe_interfaced_flag =’N’ will never be picked up. 

The following fields are updated on "oe_order_lines_all" table during Interface Trip Stop
1. Shipped_quantity
2. Shipping_quantity
3. Actual_shipment_date

Above is just simple input about basic process for Interface Trip Stop, apart from it other feature of Interface Trip Stop are
1. Line splitting
2. Progress the Order line to FULFILL Defer Status (depend on the workflow defined).