Last updated on OCTOBER 28, 2016
Applies to:Oracle Shipping Execution - Version 126.96.36.199 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 27-OCT-2016***
Executable:WSHINTERFACE - Interface Trip Stop
On 11.5.10 in Production:
When attempting to run interface trip stop for all eligible orders, using multiple child processes and multiple stops per batch, the following error occurs.
This error does not occur when ITS is run for all eligible orders, using 1 child process and 1 stop per batch.
The error message occurs at the time Interface Trip Stop is run, and may not be observed until later when customer is attempting to interface unprocessed shipping transactions. Therefore, it may not be possible to determine that multiple child processes were used. However, when ITS fails with the above error, a single order line has multiple delivery details, and some of the delivery details are interfaced while other delivery details on the same line fail. It is reasonable to conclude that use of multiple child processes for Interface Trip Stop has caused this issue.
The issue can be reproduced at will with the following steps:
1. Create 4 orders with 38 lines. Each line had a qty of 7
2. Pick the orders
3. In the Shipping transactions form:
a. Split each order line into 7 different deliveries on each of the 4 orders.
b. Assign a different delivery to each of the delivery details.
4. Ship confirm with the Defer Interface checkbox checked.
5. Run the Interface Trip Stop with multiple child processes and multiple stops per batch
6. Interface Trip Stop ends with warning " ORA-20002: 3133: Activity instance 'SHIP_LINE' is not a notified activity for item 'OEOL/xxxxxxx'"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms