My Oracle Support Banner

Shipment BASE_COST Stored In Database At Last Available Exchange Rate Date (Doc ID 2547259.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Transportation Management Cloud Service - Version 18 and later
Information in this document applies to any platform.

Symptoms

When having preference currency different from default USD, but editing a cost in USD and saving it, the exchange rate applied is the last one defined and not the one defined in the rate.

This can be reproduced with the following steps:

1. Create Exchange Rates for 2 currencies with different rates over several dates. For example:
Exchange rate: USD-EUR
Exchange date: 17.01.2019 exchange rate 1.2
Exchange date: 21.03.2019 exchange rate 1.5

2. Create a shipment on available currency date. Initial cost of the Shipment 100 USD/120 EUR (calculated at exchange date 17.01)
Updating the cost to 17 EUR - expecting USD cost to be = 14.16666 ( for exchange rate 1.2)

3. Verifying the SHIPMENT_COST table:
select * from shipment_cost where shipment_gid = <shipment_gid>
COST_BASE is 11.33 (17/1.5 which is the exchange rate for 21.03, although the EXCHANGE_RATE_DATE in the table is 17.01)

The values in the UI is correct, however this is affecting other reporting tools that are using the data from the tables.



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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.