SET EXCHANGE RATE Stores Different Value in UI And DB
(Doc ID 2467273.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Transportation Management - Version 6.4.2 to 6.4.3 [Release 6.4]
Information in this document applies to any platform.
The cost_base column in shipment_cost table is being incorrectly updated to a value based on the 'DEFAULT' exchange rate instead of the custom exchange rate as assigned on the shipment_cost record.
OTM UI shows the correct conversion based on the custom exchange rate but the table gets updated with conversion from DEFAULT exchange rate.
However, in ALLOCATION_OR_LINE_D table, cost lines are converted correctly as per custom exchange rate.
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