Performance Issues When Performing Allocation With VOLUME DIRECT DISTANCE
(Doc ID 2777335.1)
Last updated on AUGUST 12, 2022
Applies to:
Oracle Transportation Operational Planning Cloud Service - Version 21.1 and laterInformation in this document applies to any platform.
Symptoms
When using a custom action which triggers through an agent the Standard Allocation, having the allocation rule as VOLUME DIRECT DISTANCE and glog.settlement.allocation.metric.directDistance.checkForOrderPickupAndDropoffStopsOnlyOnShipment as TRUE, when running the custom action against a single Shipment having more than 3000 Order Releases, in open processes, there is a single process running for more than 5 hours.
This also happens when the action is performed by standard action from the UI.
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 |
Cause |
Solution |
References |