Japanese - Korean Currency in EKPO Table

[Former Member]

Hi ,

In Contract creation i had entered price as 9880 JPY but it got updated as 98.80 in Table EKPO.

Suggest SAP Notes if any to resolve the issue.

Note : Decimal places for currency JPY are already set to ZERO.

Regards

Ramesh

[Former Member · Accepted solution]

Hi

In SAP standard functionality it will update tables like this for some currency. this is not an error.

if required any report/print program changes make accordingly.

Regards

Hirendra

[Former Member]

Hi Kiran ,

The results are fine for USD and EUR , problem lies with JPY and KRW.

Any more inputs from any member ?

Regards

Ramesh

[mauro_bianchi]

Hi Ramesh,

I suppose you see this value directly in the table EKPO, correct ?

Transaction SE16 is a technical view to databases/tables and is designed and created for programmers but not for normal users. You didn't encounter an error, this is just the way the R/3 works with its data internally. You have to adjust your reports according to the way R/3 handles currency amounts.

Let's me explain, the value of data stored in EKPO depends on the decimal places defined for the currency. Standard is taken as 2. Therefore the value will be the same as order price only if the currency is defined for two decimal places (default is 2).

Currencies which do not have two decimal places must be defined in table TCURX (decimal places for currency codes). You can check table TCURX for JPY - CURRDEC = 0. Zero decimal places are defined for currency JPY.

So, if you want to use EKPO-NETPR for your own applications, you must also consider table TCURX.

All currencies that do not have any decimal places at all (TCURX-CURRDEC = 0) must have EKPO-NETPR multiplied by 100.

So for JPY, if actual value is 75, it will be stored as 0,75. You must multiply the EKPO-NETPR value (0,75) by 100, to have the correct value = 75 JPY.

Note 126857 is a the technical explanation of the System behavior.

Also, please refer to note 53206 and 137626.

I hope this explains the System behaviour clearly.

Regards,

Mauro

[JL23]

the value field in the tables is technically a field with 2 decimals.

So any currency that has 2 decimals is just fine, a currency without decimals is just stored with the last 2 digits as decimals.

SAP uses a function module to display it correct to the users in the usual transactions.

But in table views like SE16, SE16N, SE17, SM30 you just will see the values as they are stored.

And if you create own Abap-Reports, then you either have to make use of this function module to get the values correct or you need to program a routine yourself .

[Former Member]

Hi,

Check the table TCURX it has number of decimal places each currency .

Thanks.