Conversion from local currency to Euro

acio

Hi All

Could You share Your experience in this conversion process (NSC from Denmark, Germany,...), please.
How many hours You spent on it and on what it depends (amount of records, granules, etc...).
We are from Lithuania and our clients wanna know how much they must reserve for this process.

Thanks

ara3n

I'm sure a lot of european companies had to go through this. Can somebody help him. I have no idea where to start. I'll try to find out and let you know.

philippegirod

The main question is : how many decimals fields did you add in the database ?
The standard Euro Conversion Tool (care, it has been made in an old version) translate all the standard Local Currency fields to the new currency. You'll have to add in this process all added currency fields (for instance, if you added in the Customer Table, a new "Credit Limit 2" field, you'll have to add it in the conversion tool.

The necessary time is not really important : if there are no specific currency money fields : one day, but 1 day during which no user can use the database. It is preferable to have a test day before, then some users can see if every thing is OK.
Else, you'll have to change the tool, so you'll need arround 1 day more.

Note : that's difficult answer your question without knowing anything about the database you have to convert in EUR...

Kowa

The actual conversion process totally depends on how many ledger entries there are. Our companies database ( I wasn't working for an NSC then, changed sides later ) was about 40 GB, and it took about 2 days. All amounts connected to the LCY and the SIFT-Fields in the Ledger Tables have to be recalculated,this takes up most of the time, you can disable some secondary keys to speed this up , but of course these have to be reactivated. You can create historical tables for the old currency, but this will take some extra time of course ( and space)
There was also one bug in the euro conversion , one field was divided twice by the conversion factor but no one could find out the reason. Luckily we discovered this on time and copied the field value to a extra field to write it back after the conversion. Apply it on a test database and check all fields first before going live.