Interface Trip Stop Process Running Long For Large Deliveries
(Doc ID 1988388.1)
Last updated on DECEMBER 10, 2024
Applies to:
Oracle Shipping Execution - Version 12.1 and laterOracle Advanced Pricing - Version 12.1 and later
Oracle Order Management - Version 12.1 and later
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
Interface trip stop takes 5 hours when running for a large amount of records such as 53,000.
The following is identified as the most expensive SQL statement:
Customer does not want to defer the Interface Trip Stop process and run it individually using "Interface Trip Stop - SRS" because they would cause dead locks as detailed in note below.
They have scenarios where the same order could get shipped in multiple deliveries: Deadlocks occur when Multiple ITS processes are running (Doc ID 822636.1)
STEPS TO REPRODUCE THE ISSUE
The issue can be reproduced at will with the following steps:
1. Ship Confirm API
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |