Skip to Content
0
Former Member
Dec 20, 2006 at 02:18 PM

FOX-formula in multiplanning area

36 Views

We are using BW-BPS in BW 3.5.

We have a multiplanning area with two cubes. One cube with budget data and one cube with shares (a number between 0 and 1). The budget data are initially loaded and contains 100% numbers (i.e. the income loaded is all income for that asset). The shares will be used to calculate our client's share per asset.

The share is only dependant on asset and fiscal year, so that's the only charcteristics in that cube. In the budget data cube we have the characteristics asset and fiscal year as well, but also several other characteristics, like activity and budget version. There is also a characteristic specifying if the record holds 100% values or just our client's share.

We have written a FOX-formula to calculate our client's shares:

DATA YEAR TYPE 0FISCYEAR.
DATA ASSET TYPE DIPASSET.

FOREACH YEAR.
  FOREACH ASSET.

    {ZKB_AMNT, YEAR, ASSET, J, ZPABLTB} = {ZKB_AMNT, YEAR,
ASSET, N, ZPABLTB} * {DIPASTSHA, YEAR, ASSET, #, ZPABAST}.

  ENDFOR.
ENDFOR.

The syntax is {key figure, fiscal year, asset, share type, planning area}.

The problem is: In the new records being created by this formula, activity, budget version and other characteristics not included in the "Fields to Be Changed" do not get a value. We would like those characteristic values to be copied from the records being read from the budget data cube. If we remove the share part of the formula (

* {DIPASTSHA, YEAR, ASSET, #, ZPABAST}

), all the characteristics do get a value.

We tried to fix this by including all the other characteristics in the "Fields to Be Changed" and expanding the FOREACH-loop to include these characteristics. That resulted in a process running until it timed out. Probably the system then combines all different combinations of characteristics, and that is way too many.

I guess it would work if we included all the other characteristics in the share cube, but we don't want to specify the shares that detailed.

Any better ideas?