Last updated on JULY 24, 2017
Applies to:Oracle Transportation Management - Version 6.3.2 to 6.3.4 [Release 6.3]
Information in this document applies to any platform.
When there is secondary charge shipment present, shipment actual UI may pick the secondary charge shipment to send into the backend logic to process. This would cause order movement being created incorrectly for secondary charge shipment and recalc logic not triggered correctly. From the user side, this is views as the "double save" issue
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms