REST API GET Call for OTM Rate Records Gives Currency Always in USD, Irrespective of the Rate Record Cost Currency
(Doc ID 2930086.1)
Last updated on FEBRUARY 22, 2023
Applies to:Oracle Transportation Management Cloud Service - Version 22.3 and later
Information in this document applies to any platform.
In REST API GET call for OTM Rate Records, cost currency is always displayed with currency USD in the REST call response payload. It is not displayed in the currency in which the rate cost is defined in the system. In such cases, the cost value is converted into USD calculated value based on the Currency Exchange Rates defined.
Rate details should be displayed on the REST API response payload as this is entered in application.
For example, if a Rate Cost currency is defined in Local currency like INR, then it must be displayed as INR.
Steps To Replicate
The issue can be reproduced at will with the following steps:
1. Define a Rate Record Cost with currency INR
2. Perform a REST GET call for that rate record
3. REST GET Response will come with Rate converted into USD and currency as USD
If any User Preference is there for Currency, and the Exchange Rate is present for USD, then that User Preference Currency will come in the GET Response.
This is not in scope of this document's purpose.
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