FOX - To work with Characteristic as Key Figure.

[former_member187400]

Hello All -

I am working in BPC Embedded Planning BW 7.4 SP12, and Analysis for Office.

I have Planning Layout:

Account | Flag | Quantity | Multiplier

00001 | ON | 10 | 50%

00002 | ON | 20 | 70%

00003 | OFF | 20 | 70%

I used characteristic as key figure to capture the flag in the Input Planning. The Flag & Multiplier (Key Figure) are stored in DSO, and I have the Quantity where it's stored in Cube. In the planning, the Flag is a key figure.

The Flag will have value: "ON", and "OFF" and I need to create FOX Formula to calculate the Net Value.

I will create Fox with the condition FLAG = ON, and will calculate NET = Quantity x Multiplier.

The issue is in the FOX, I cannot put the FLAG as a Characteristic Condition.

The question is what to do to be able to have FLAG in characteristic Condition or, how I run the logic with Condition FLAG = ON?

Kindly please ask your advice,

nb:
FYI, this is error message that I found :

'YXPENTONF' is a characteristic or a unit characteristic in the data part of DataStore object 'YXPPMD42'. 'YXPENTONF' is also used in the aggregation level. This is not supported.

Many thanks,

Daniel

[venkatasreekar_krothapall · Accepted solution]

Daniel,

I think the issue here is with setting up FLAG dimension as 'Key Figure'.

Why do you want to define FLAG as 'Key Figure', especially when it's holding alpha-numeric characters (ON, OFF) ??

Try defining FLAG as a Characterstic and then use it in a condition within the FOX code.

Let us know if that works.

Cheers!

[gregor_dieckmann · Accepted solution]

Hi Daniel,

the feature 'characteristics as key figures' allows to expose characteristics contained in the data part of a DSO as a 'key figure'. This allows to use a characteristic as a key figure in queries, e.g. one can restrict the 'key figure', drill-down is not possible (with is natural since characteristic is in the data part of the DSO).

In planning this kind of 'key figure' is 'virtual', i.e. the key figure is not really contained in the DSO (but the characteristic is). Internally the characteristic value (as a key figure) is transported as a SID value (an integer) and converted to the characteristic value for the clients. As a result,  by now only planning function types not touching these kind of key figures are supported, cf. the documentation. E.g. 'copy' works but not FOX.

In your case to use a real key figure in the DSO would be enough, e.g. of integer type. Then you can make the convention 0 is OFF and the rest is ON. In a FOX you can then just use IF statements to do the calculation you want. A condition is not needed.

Regards,

Gregor

[former_member187400 · Accepted solution]

Many thanks Gregor / Venkata ,

The reason why I use Characteristic as Key Figure is user can see 'ON' or 'OFF' in the layout instead 1 or 0.

In the summary, can I say that Characteristic as Key Figure is not supported in FOX? and if I still want to go with this design means that I need to go by Exit Planning Function?

Many thanks,