Decimals places to 4

[Former Member]

In my layout I am using 0AMOUNT and US$4 with 4 decimals. When I key a number into the layout, regardless of what it is, it is correct in the layout. However, when I look in the cube or query, if the value I put in the layout is equal to or less than .0040, it appears as 0. If I put in .0041 or higher, I see that value in the layout and also in the cube and query.

Thanks, Keith J

[Former Member]

Keith,

Try with Data Type FLTP (Floating Point number) in Key figure definition.

Thanks,

Ravi

[Former Member]

Keith,

I believe 0amount is of type CURR if I remember correctly and in BPS, regardless of how you specify display for currency, the accuracy is only to 2 decimal places and they tend to round down / trucate the digits after the 2 it recognize.

We ran into issues with distribution in that if we display only $ in layouts and run functions, $100 into 12 months became 8.33333 which got rounded into 8 and stored thus the year became $96. I tend to have to display months as $.nn and that gives me $8.33 per month or total of 99.96 and we lose precision of 4 cents from the distribution. It may not sound like a lot but they add up if you are doing cost center / cost element.

If you truly need more precise numbers, don't specify CURR but use a floating type infoobject.

Hope this helps,

Mary

[Former Member]

Forgot to mention that the 2 decimal place is due to the specification of USD in the currency tables.

[Former Member]

Sai,

I made the change to 5 decimal places, but it responded the same. Anything less than .0041 still shows up as 0.

Other ideas? Thanks, Keith

[Former Member]

Keith,

On the Query, under the properties of 0AMOUNT, did you extend it the decimal places to show 4 decimal places?

D

[gregor_dieckmann]

Keith,

I think you used note 460652 to change length and decimals of domain RSKYFAMO and overlooked that it is not allowed to change the number of decimals. Here only 2 decimals are allowed. In SAP systems currencies always have two decimals, exceptional currencies are maintained in table TCURX. So all currencies not in TCURX have 2 decimals.

So in BW systems currencies on the DB have always 2 technical decimals, how this value is interpreted comes from default 2 or the TCURX settings. So the system get confused if you change technical decimals since this is always assumed to be 2.

Be careful to change TCURX settings when you have data on the DB, since as explained above the data will be interpreted in a different way.

Example:

1 EUR on DB 1.00, no TCURX entry

1 JPY on DB 0.01, TCURCX setting 0 decimals

Regards,

Gregor

[Former Member]

Keith ,

have u set the 4 decimal point in your planning level-> manual planning?

[Former Member]

Hi Keith,

i guess the Floor value of the number is taken in here to diplay both in the layout and also in the cube.hence you aren't able to see the values.is it okay for you to use a 5 decimals values?.just for some validation purpose ,pls use a 5 decimal place value object instead.

regards

Sai Vishnubhatla