12-26-2017 7:13 AM
Hi,
ALV grid is showing wrong value in display. User setting is Decimal Notation X 1,234,567.89 so it means decimal value separated by '.' . Now i have 2 screen shots. In debugger it shows different value and SE11 display it shows different value.
In debugger:
In SE11 display:
Version: SAP 7.5
Amount Field data type as CURR
Length 28 and Decimal 4 places. and currency is USD and for this no decimals are maintained. so by default its showing 2 decimal in display but values are wrong.
So what should we do for correct display any notes or any $sync tcode we have to run?
Any suggestions what we should do here??
12-26-2017 7:35 AM
As i know, actually there is no different with 2 pic above. just different in screen output visual.
in curr fields, sap store data to db (value divided by 100), so when you get data you have to multiply with 100.
hope this can answer your quest.
12-26-2017 8:05 AM
Thanks Proyek for quick reply. I am not sure of (value divided by 100) theory correct or no. lets take example if i enter 21.43 then as per theory sap will store this as 00.2143 and while display its showing as 2,143.00. so is it sap multiplying by 10000 ???. Its display issue can we correct this??
12-26-2017 10:39 AM
It doesn't work exactly as described by proyeksyariah .
It's not always a division by 100. The position of the decimal point of currency amount fields (field of type CURR) is exclusively determined by the value of the currency key field (of type CUKY) related to the currency amount field. If it's related to currency USD or EUR (and many others), it's 2 digits after decimal point (variable with numeric value 15.4100 means 1541.00 EUR or USD). For JPY, there's no decimal point (15.4100 means 154 100 JPY).
More information in note 1679403 - Currency Amounts and the Type CURR in ABAP
12-28-2017 8:48 AM
Hi, Thanks for the help. When I enter only 25 value on amount still it gets converted to 2,500.00. Do we have any option see the value which we enter in amount fields? In a display, it looks like wrong.
Regards,
Prashant.
12-28-2017 9:09 AM
Please read the note, it explains why it behaves like that, and you'll understand that it's completely logic and then you can find the solution.