My Oracle Support Banner

When Default Retain Exchange Rate Type = No and Rate Type Is USER in The Primary Ledger, Rates in The Secondary Ledger Journal are Not Replaced (Doc ID 2057950.1)

Last updated on MARCH 07, 2023

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.


Customer has a Primary ledger with currency CUR.
The Secondary Ledger currency CURS.
The conversion rate between these two currencies = 1.

Our requirement is that  foreign transactions created in Primary ledger should be converted in Secondary Ledger using different exchange rate type.
For example:
A journal in the primary ledger is created using CORP rate type.
When this transaction is transferred to the Secondary ledger it should use the 'NEWDAY' exchange rate type.
We have achieved this by populating the default exchange rate type field = 'NEWDAY' and Retain Exchange Rate type = No for the Primary/Secondary Ledger mapping.
This works correctly in most cases.

But we are facing with any issue when transaction uses USER exchange rate type.
In this case, the  system does not take into account setups made on the Mapping page.
The rate type in the secondary ledger stays as USER. 
The  User  rate is  treated differently by system compared to as other rates types.



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

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