Increasing Keyfigure length in Production System

[Former Member]

Hi Experts,

I want to increase the length of a keyfigure (standard infoobject) from 3 to 5. The keyfigure is used in multiple targets of production system.

I am planning to change the domain associated with the keyfigure with a custom domain and change the entries in RSDKYF table.

But i am worried about the data which is  already loaded in data targets.I just want to keep the old data as such and load future data with required decimal places.

I am not in a position to think about reloading.

Please suggest the consequences of increasing the keyfigure length.Will it work perfectly if i transport the custom domain and the keyfigure to the production system.

Thanks,

Minu

[former_member184494 · Accepted solution]

Minu,

A key figure is a number - it does not have a length...

You could change it from Dec to Float if required. If you change it to a custom domain - I am not sure how the aggregation behavior of the data will work. I dont think you can aggregate the values of a key figure if it is on a custom domain.

The best bet if this is a key figure will be to change its type (Decimal to Float for example ) and transport it. The data should adjust itself but will take some time for the transport to go in if the data volumes are high.

Also if you are changing - then you need to reactivate the data source and all other dependent objects for this change to become visible in the transformations and otherwise.

[Former Member · Accepted solution]

Hi Arun,

Thanks for the reply.

I want to increase the decimalplaces of exchange rate "0EXRATE_ACC" infoobject.

Associated domain is "RSKYFNUM" which supports only 3 decimal places.But we need the infoobject with 5 decimal places in future.

Do we have any successful option to handle this requriement without doing the rebuild in data targets as the business needs only the future records with required decimal places?

Thanks,

Minu

[former_member184494 · Accepted solution]

Not sure if both these questions are related :

I have a few questions :

1. when you check the TCURR table - it has 5 decimals

2. When you apply an exchange rate - it uses 5 decimal places to convert

The issue is that you are using a Key figure of type CURR which restricts the display to 2 decimal places and the values are rounded up.

AFAIK - there are two options :

1. When calculating the value in the data load - multiple the Key figure by 100000 and then convert it and then divide it by 100000 when reporting ( use NODIM in a formula and you will get your 5 decimal places)  - here it will be a change in the data flow - but since you are looking at future periods only - you can still do it in the query and it will affect future periods only

2. Add another Key figure to the cubes and use the currency conversion in the routine to store 5 decimal places - but this will require a reload or smart handling using IF Statements in the query builder. - you will however lose the capability of currency translation in the query at run time.

[Former Member · Accepted solution]

Thanks Arun...First option suggested by you solves the issue.

Thanks Again,

Minu