When you use ConversionHourInGMT, the migration code attempts to use historical currency conversion rates for money objects whose transaction date is in the past. You must provide historical conversion rates to properly convert these money objects. If you have not loaded the proper rates, any historical reporting you do will be based on the latest conversion rates and not on the ones in effect when the transactions were performed. (EMU currency rates have been frozen for a few years, and will be used as necessary.)

Set these system parameters during the euro conversion process:

Set EnableEuroDualCurrencyDisplay to true to use dual display in all reports. By default, this parameter is set to false. You must set this parameter on a per-partition basis.

Set ShowCurrencyPrefixSuffixInCSV to true to display a second column in CSV reports that contains the currency descriptor (such as EUR). This is useful for transaction reporting (where each money amount may be in a different currency) because reports will clearly display the transaction currency and euro equivalent.

Add ConversionHourInGMT and specify the hour of each day to look up currency conversion rates. The hour specified should be relative to the GMT time zone. By default, it is zero (midnight). You should specify an hour that is immediately after the hour when your conversion rates are loaded. For example, you might use the following statement to convert base currencies relative to 4 am GMT time:

FixupSystemCurrencies = {
ScheduledTaskClassName = "ariba.tool.migrate.currency.FixupSystemCurrencies";
OldBaseCurrency = “Old EMU Currency Unique Name”;
ConversionHourInGMT= “4”;
};

Additionally, change these existing parameters:

• Set Base Currency to EUR to change the system's base currency from EMU to euro.
  
• Set Default Currency to EUR to change the system's default currency from EMU to euro.
• Set reporting currency to old base currency, if you want to facilitate error checking and preserve old data.