Number of places after decimals Livecache can store and display

[Former Member]

Hi:

THis is regarding the number of places after the decimal that Livecache can store and display. There has been a previous thread on this. The link to that thread is below

If a Key Figure has a unit, there are two ways of representing it: i) Quan Type with Quan as the Data Type - in this case, the number of decimals in BW will be 3, and, ii) Quan Type with FLTP (float) as the Data Type - in this case, you can have upto 16 places including the decimal.

Let us take the case where we have selected Quan Type and FLTP as the Data Type. Assume that we have a key figure X whose value is 123456789.123456 (this is a total of 16 places including decimal which can be stored and displayed in BW). Now we bring this data into DP Planning Area where the data is stored in Livecache. Livecache has its own data representation and according to documentation (and my testing) is able to store and display data up to a maximum of three places after the decimal.

Consulting note 389760 says the same thing although this is an older note.

One workaround that has been mentioned is to work with a UOM that is coarser than the base UOM (Kilo Gram instead of Gram for example).

Does anyone know of any recent notes / support packages that could change this situation and Livecache can store and display more number of decimal places?

Thanks in advance

Satish

[Former Member · Accepted solution]

Hi Satish,

You have done very good analysis. The note 389760 is still valid.

We can just calculate and display the values in the planning book with a specified number of decimal places varying between 0 and 6. If you are trying to store the material price value as 0.00050 (for example) in the LiveCache that is not possible. It will always be stored as 0.000. But if this value is calculated using a macro(or otherwise), then it can be displayed as 0.00050.

So i am sorry to say this, there is no new note in the recent upgrades(even in SCM 7.0 Release) and saving in livecache is only possible upto 3 decimal places.

Thanks and Regards,

Nithin.

[Former Member]

The three decimal places with live cache exists. There is no work around for this. So, planning for more than three decimal places is going to be a complicated process.

One of the things that we tried at my implementation is the following: plan for 6 decimal places in DP planning table. At the time of save, save this into a temp key figure after multiplying it by 1000000. Then, you come back into the planning table, take this temp key figure, divide it by 1E-6 and then bring it into the original key figure. Not a very elegant way of doing things but it works.