Re-configure JPY currency

[Former Member]

Hello peeps,

Good evening!

I want to ask again your help regarding currency configuration specifically for 'YEN'.

Is it possible to set the JPY currency to 2 decimal place just like the USD currency? If possible, how? Is there any effect with the existing data or transactions in the system?

Hope you can give me a bit of advise..

Thank you very much..

April 😃

[Former Member]

OY04 is the tcode where you make this change.

Here is an extract of the warning that SAP posts for such changes :

In the R/3 System tables currency fields are stored as decimal figures with a variable number of decimal places. The decimal point is not stored in the field in the database. Instead, each currency field refers to a currency key field. In this transaction you assign the number of decimal places to this currency key uniquely.

Example: If you have set currency USD to have two decimal places and you post an amount of 100 USD, an amount of 10000 USD is stored in the currency field in the database. Not until this amount is processed further or is output does the system use the currency key from the reference field to determine the number of decimal places via this table. In this way the table content can be interpreted correctly for further processing or formatted for output with the correct Punctuation.

If after posting you changed the number of decimal places for USD, for example, to 3, the existing field content of 10000 would be interpreted for futher processing or output as 10 USD (10.000). This would mean that the contents of tables across the system would, for all currency fields containing an amount in USD, be interpreted incorrectly by 10 per cent. To change the number of decimal places for a currency already in use, you must convert all the tables in the R/3 System that contain currency fields, so that the data integrity

remains. This cannot, however, for both organizational reasons and under the runtime aspect be carried out in a productive system.

The following changes to the TCURX table can thus lead to the loss of data integrity if you make the changes in a productive system or transport them into a productive system:

o Change to the number of decimal places of an existing currency

o Deletion of an entry from the TCURX table

o Deletion of an entry from the TCURX table (corresponds to changing the decimal places to the standard value of two decimal places)

o Insertion of an entry in the TCURX

(corresponds to changing the standard value of 2 decimal places to a different value), if this is a currency code that already exists

Uncritical changes are any made to this table during the Customizing of a new installation or the insertion of TCURX even during operations, if the currency codes have just been entered in the TCURC table using transaction OY03, signifying that no postings to these currency codes can have been carried out yet.

[Former Member]

Why do you want to do that? As you know, Japanese YEN and Italian LIRA don't have decimal places. YEN is the lowest form of currency, so there is no physical currency equivalant for say 1.5 YEN or at least that is the rational behind this setting.

Changing the number of decimal places has a system wide ramifications, particularly, if you are already in production.

Consult a functional/business expert before you take this step.

[Former Member]

Hi

I also same kind of requirement that is ,to change of decimal places of an existing currency from 2 to 3. Now you tell how you do this activity . also how existing data saved based on 2 decimal places get converted according to new changes i.e 3 decimal plaaces. I have huge amount of such data.

Is there any utility in sap for this conversion before or after change.

please reply soon. this is very urgent.

Thanks

ruchika

[former_member223537]

Hi,

Japanese currency doesnt have a DECIMAL in it. So i dont see any reason why you want to convert it with 2 decimal places.

Best regards,

Prashant

[Former Member]

Hi Prashant

I am working with japense currency. I need to change existing currency decimals from 2 to 3 in such way that existing data can also be updated/converted. Or how data conversion is to be done to avoid impact due to this change.

Can you help me in this regard

ruchika

[vtr1cob]

Hi,

I am also having the same requirement. My Japanese customer is asking for 4 or 6 decimals , may be it is industry specific requirement. Price of 1 unit of many materials is less than 1 JPY.

Expecting some solution from some experts. We all know the standard settings for JPY is a big "Zero".

But, if needed, can we change and what are the risks?

regards,

VTR