Interface Trip Stop (ITS)

In 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.   OM Interface occurs first,  then Inventory Interface

You can also run Interfaces Individually for Order Management and Inventory.  However, the system will not allow you to run Inventory Interface until Order Management has completed successfully.

The Delivery Detail status becomes Staged/Picked after Pick Release is successful.
Thereafter when you ship confirm the delivery to which this Delivery Detail  belongs,  there are the following cases that could happen:

Case 1:
======

If you ship confirm the delivery and do not run the interface (you Checked the Defer Interface Flag in the Confirm Delivery window before ship confirm), the delivery detail status would become "Shipped". This signifies that the shipment has left the Warehouse and therefore the Delivery Detail status become "Shipped".  However, the data is still not interfaced to OM and Inventory;  which means that information such has quantity shipped is not reflected in inventory on-hand and transactable quantities for the item in question.  If delivery details exist in this status,  shipping transactions have not completed (there are unprocessed shipping transactions),  and you will not be able to close the current month inventory period until the interfacing is performed.

Case 2:
=======

If you ship confirm the delivery and RUN the interface (you did NOT Check the Defer Interface Flag in the confirm delivery window), the delivery detail status would become "Interfaced". This signifies that not only has the shipment has left the Warehouse,  but also the data related to the delivery has been interfaced to Order Management and Inventory.

Note:
Please note that the Delivery Detail status will remain "Shipped" till both Order Management Interface and Inventory Interface have completed successfully. Even with Order Management Interface completed successfully and Inventory Interface Pending, the Delivery Detail status will remain as "Shipped"
The significance of the new RELEASE_STATUS is that it lets the users know whether the delivery details has been interfaced to Order Management and Inventory or not .

What is the ship confirm process of move a sales order issue to inventory?

For a SO Issue, the trip stop program (WSHINTERFACE) inserts the record into the open interface with a transaction mode of 3- Background but the trip stop remembers the transaction id and continues to process it through to completion using an online transaction process routine unless you use the profile option WSH: Defer Inventory Process Online as noted below.  The flow is something like this:

STEP 1: Create book and pick an order
STEP 2: Run the Ship Confirm.
STEP 3: within the ship confirm process, order management runs the trip stop program.
STEP 4: The trip stop program inserts into the transaction open interface
STEP 5: The trip stop processes the transaction and runs the inventory transaction manager.

Here are some more details about routines being called while these steps are executed:

STEP 1: Create book and pick an order
STEP 2: Run the Ship Confirm.
STEP 3: within the ship confirm process, order management runs the trip stop program.
Trip Stop (WSH_SHIP_CONFIRM_ACTIONS.interface_all)
om_Interface_Trip_Stop
Inv_Interface_Trip_Stop
Interface_Delivery_to_Inv
interface_detail_to_inv
wsh_trx_handler.insert_row
STEP 4: The trip stop program inserts into the transaction open interface
insert into mtl_transactions_interface
STEP 5: The trip stop processes the transaction and runs the inventory transaction manager.
Inv_Interface_Trip_Stop (We were already here from step 2c. Now we continue.)
process_inv_online
mtl_online_transaction_pub.process_online
Locks the interface transaction
inv_txn_manager_pub.process_Transactions -- This routine does all the validation.

You can set up and run Interface Trip Stop - SRS by the following navigation path:
1.OM Super User Responsibility-->Shipping-->Interfaces-->Run-->
2.Select Interface Trip Stop - SRS from the Name field
3.Set the Mode to All and keep all parameter as defaulted value is recommended.
4.Click OK
5. If you want to run it periodically, click on the Schedule button.
On the Schedule window you can set this job to be run:
 a) As soon as Possible
  b) Once
  c) Periodically
  d) On specific days

Issue:Failure to regularly gather schema statistics will place unwanted additional
processing loads on application jobs and concurrent programs
. Frequent house-keeping and refreshing of schema
statistics will ensure all meta-data for application process is current and
timely.

Solution

1. As "Sys Administrator" responsibility
2. Run Reports
3. Select "Gather Schema Statistics"
4. Enter required parameters, including WSH and INV schema names.



ISSUE:The Interface Trip Stop process does not launch automatically when pick confirming sales orders through a custom concurrent program.

How do I get the Interface Trip Stop to run automatically when Ship Confirming ?

Solution:

This behavior is controlled by the - Defer Interface - Attribute in the Shipping parameters or Global Parameters setup in Shipping.

To check the Ship Confirm Rule setup:

Navigate to Shipping --> Setup --> Ship Confirm Rules.
NB - you need to confirm that you are in the correct shipping organization when doing the following
Search for the Ship Confirm Rule that you are using then view the following attributes:

Set Delivery In-Transit
Close Trip
Defer Interface --- this should be deselected

To check the Global Parameters setup:

Navigate to Shipping --> Setup --> Global Parameters

View the - Defer Interface - attribute --- this should be deselected.