Oracle Order Managment - Interface Trip Stop

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.