APO DP: Forcing disaggregation by new proportions?

[Former Member]

Hello all.

Does anyone know if it's somehow possible to force a re-disaggregation in APO DP ?

When you enter a figure at an aggregated level the value is distributed to the lower levels according to the aggregation setup and perhaps the proportional factors calculated based on some other key figure.

But!

What if the proportional factors change? Is there some way to force the split to happen again without actually updating the field?

It'd help us a great deal if we could do some kind of batchjob or macro that could do the split again if the proportional factors change.

Does anyone know?

[Former Member]

Hi Simon,

This is possible with a macro function. We currently do this in one of two ways.

Let's say that key figure A disaggregates according to key figure B (this setting must be made in the planning area settings).

The first way would be to create a series of macros where

1. the value of key figure A is copied to key figure C or an auxiliary key figure

2. key figure A is set to zero

3. the value from key figure C or the auxiliary key figure is copied back to A, whereupon the redisaggregation occurs.

The limitation of this method is that you need to separate out the steps in different macros, because the zero value of the second step has to be saved to liveCache before the third step can happen. If you do it this way and find that the redisaggregation didn't work, then you may have to run them in different 'activities' so that liveCache gets updated between each step.

The second way (if you are using SCM 5.0 or higher)

1. Create a macro

2. Add a macro step

3. In the macro step, make key figure A equal to key figure A (yes, this is possible!)

a. In the macro step, set the change mode from 'Value Change' to 'Redisaggregation'.

This works well for us but we only run it in background jobs because using a redisaggregation macro interactively makes the dataview act unpredictably. Specifically, the values from other fields that were not directly involved in the redisaggregation calculation disappear from the dataview. We found that the values weren't changed at all and could be restored by reloading the selection, but it was alarming to the planners when this happened.

Hope this helps!

Dan

[Former Member]

Thats's a very clever solution, i think that could work for us as well. Thanks a lot!