Is There Anyway To Capture Detail Logs of ITS Failure When It is Spawned From 'Ship Confirm'
(Doc ID 2548276.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Shipping Execution - Version 12.2.6 and later
Information in this document applies to any platform.
Is there anyway to capture detail logs of ITS failure when it is spawned from 'Ship Confirm' ?
When the User does a 'Ship Confirmation' from the EBS Forms (ISO Shipment), the program internally fires 'Interface Trip Stop'
This is not interface trip stop srs but interface trip stop
Here is the example again
1. When the User does a 'Ship Confirmation' from the EBS Forms (ISO Shipment), the program internally fires 'Interface Trip Stop' which we see completing with Warning.
Customer has provided a log file for the same which shows that … Lock could not be obtained. All the Warnings have the same message.
2. This is leading to material not Interfaced from the Shipping Org and hence cannot be received at the Receiving Org. Thus someone has to run the program 'Interface Trip Stop - SRS' with Delivery ID as parameter. In order to find out the cause of the Lock, we run this program with Debug Mode = ON. But whenever we run this Program, it completes normally so we do not know the root cause as to why it had failed the first time during 'Ship Conformation'.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document