Interface trip stop ITS in Oracle Order Management

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.

=============================================================

In Oracle Order Management, Interface Trip Stop (ITS) will be trigger at the time of Shipping if check box “Defer Interface” is not check.
Automatically: The request will be executed upon ship confirm if the delivery is not assigned to a trip, or the Defer Interface check box is not selected. If the delivery is assigned to a trip, the Interface Trip Stop concurrent request program will be run automatically when the destination Trip Stop is closed. If the delivery is not assigned to a trip, and at the time of ship confirm the Defer Interface is checked, the Interface Trip Stop concurrent request will be automatically run when the destination Trip Stop is closed.

Interface trip stop has Two parts 
1. It process the data related to Order Management. 
2. It Process data related to Inventory.and we have separate Concurrent Process for this - Inventory Interface. 
In First part it make update on oe_order_lines_all table as well as wsh-delivery_details and once this part executed successfully only then second phase of ITS has triggered. If first part error out for some reason then 2nd part will not be triggered Inventory Interface will be trigger only if the first part, that means related to OM has successfully completed and flag OE_INTERFACED_FLAG = ‘Y’ on WSH_DELIVERY_DETAILS.If value of this flag is N/P then Inventory Interface will never be triggered. And even if you try to submit the Inventory Interface from SRS, delivery detail with oe_interfaced_flag =’N’ will never be picked up. 
ITS update the following fields on oe_order_lines_all table 
1.Shipped_quantity
 2.shipping_quantity, 
3.Actual_shipment_date 
Users submit the interface trip stop while doing the ship confirm, but there are considerable cases when customer preferred to run this as a scheduled process without specifying the delivery# or Trip #, because their volume of order processing is very high and they want to run this process during some particular time of the day. 
ITS can also be executed from concurrent request. To manually execute the concurrent request, navigate to the Shipping Interfaces form and select Interface Trip Stop-SRS from the Name field. The parameters window will be displayed. 

OM Super User Responsibility : Shipping>Interfaces>Run 
Mode: You select the interfaces that you want the process to run against. The list of values contains the following choices: •All •Inventory •OM and DSNO 
Trip Stop: Select a trip stop that you want to run the process for. The list of values will display all open trip stops.
 Delivery: Select a delivery that you want to run the process for. The list of values will display all open deliveries. 
Debug Level: This is the debug log level that is used when attempting to identify the cause of an error. You can enter zero (0) for Off and one (1) for On. 
Organization: If you select an organization, then all eligible trip stops for the organization will be processed. Trip Stop and Delivery fields must be left blank if you use this option. 
Number of Child Processes: The number of child concurrent programs that should be run in parallel and is defaulted to one. If the number is not greater than 1, then the Interface Trip Stop will not run the child processes in parallel, instead the Interface Trip Stop process itself will finish the process. 
Stops per Batch: Indicates how many trip stops should be processed per child request and is defaulted to one. 
Profile Option: Following Profile Options need to be set before each test case, then reset after completion: 

OM: Debug Level = 5 

Edit > Preferences > Profiles > F11 > OM: Debug Level > Ctrl+F11 -> Set User Value to 5

WSH: Debug Enabled = Yes 

Edit > Preferences > Profiles > F11 > WSH: Debug Enabled > Ctrl+F11 -> Set User Value to Yes

INV: Debug Trace = Yes 

Edit > Preferences > Profiles > F11 > INV: Debug Trace > Ctrl+F11 > Set User Value to Yes

Following Profile Option once set do not need to be changed. Please confirm settings per Note 290432.1 How to Create a Debug File in Shipping Execution

WSH: Debug Log Level = Statement

INV: Debug Level = 10

Navigate: Navigate to the Interface Trip Stop concurrent request (Interfaces > Run > Single Request > Interface Trip Stop - SRS).

Parameters: In addition to other parameters, set the Debug Level parameter to 1 (Debugging ON) and submit.

Output: To retrieve the output navigate to:

View > Requests > Find > click on View Log... for Interface Trip Stop log file.

===========================================================================================

Interface Trip Stop Functionality

There are typically four interface program get triggered at the time of ship confirm. They are 

• Interface Trip stop
• Packing Slip Report
• Bill of Lading
• Invoice

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

Interface trip stop has two parts

• Order Management Interface (First part)
• Inventory Interface (Second part)

Order Management Interface part update the order management tables like OE_ORDER_LINES_All (Update Shipped_Quantity, Shipping_Quantity, Actual_Shipment_Date) and also WSH_DELIVERY_DETAILS (make Released_status, OE_INTERFACED_FLAG = ‘Y’) table.

The Inv_Interfaced_Flag remains = X (Pending) or N which will changes to Y after execution of second part

The second part i.e. Inventory Interface will be triggered only if the value of OE_INTERFACED_FLAG = ‘Y’ otherwise second part will not be triggered. Even if you try to run this from SRS, these lines will not be picked for processing. 

Inventory Interface part move data from MTL_TRANSACTIONS_INTERFACE to MTL_MATERIAL_TRANACTIONS and MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Issue transaction. Also data is deleted from MTL_DEMAND, MTL_RESERVATIONS and WSH_NEW_DELIVERIES. Item quantity reduced from MTL_ONHAND_QUANTITIES and 

MTL_TRANSACTION_ACCOUNTS is updated with accounting information.

Both these parts are executed simultaneously.

For more info

http://alloracleapps.com/oracle_apps/apps_functional/om/ship-confirm-the-sales-order/