When troubleshooting currency conversion:
If you receive an error when trying to link the currency database to the main database, make sure the main database meets these criteria:
A dimension is tagged as time.
A dimension is tagged as accounts.
The accounts dimension has a currency conversion category defined for the categories of accounts that you wish to convert.
All members of the accounts dimension that should not be converted are tagged as No Conversion. The No Conversion tag is not inherited.
A market dimension is tagged as country.
The country dimension is assigned a currency name, even if each member in the dimension is individually assigned a currency name.
Each member of the country dimension has an associated currency name or inherits the currency defined at the dimension level.
If you receive an error when trying to link the currency database to the main database, make sure that your currency database meets these criteria:
A dimension is tagged as time.
The time dimension contains each member that is defined in the time dimension in the main database. Make sure that each member is included and spelled correctly.
If you use Dynamic Time Series members in the main database, you must use Dynamic Time Series members in the currency database.
A dimension is tagged as accounts. The accounts dimension in the currency database contains the account categories defined in the main database.
A dimension is tagged as country and contains the names of the currencies used in the dimension tagged as country in the main database. Make sure that each currency is included and spelled correctly.
Make sure that the currency database is started.
Errors linking the currency database with the main database (such as "Unable to Load Database") are often explained more fully in the application log.
Having the CCTRACK setting turned on in the essbase.cfg file can often be the cause of currency data not converting.
If base data results in #Missing values after conversion, make sure that the associated rate in the currency database is not set to #Missing.
In some cases, you might want to enter data in a base rate partition and convert it to a local rates partition with the CCONV TOLOCALRATE command. This does not work directly because Essbase reads the CCTRACK partition flag as "unconverted." As a workaround, first run the CCONV command against an empty partition (the one intended to hold the local data), and then move the data in. Running CCONV TOLOCALRATE against this partition should work because Essbase reads the CCTRACK flag as "converted" and thinks it has already converted the partition.
See Oracle Essbase Error Message Reference to troubleshoot specific currency-related error messages.
“Designing and Building Currency Conversion Applications” in the Oracle Essbase Database Administrator's Guide