IP planning on navigation attribute

[Former Member]

Is there any way to plan on infoobject attribute in IP?

Attributes not visible on aggregation level. Would it be adding the attribute infoobject to a planning cube the only way to plan on it?

[gregor_dieckmann]

Hi Gleb,

what do you mean with 'planning on navigation attribute'?

Having a characteristic A with attribute B, the navigation attribute A__B is automatically contained in the aggregation level if A is contained in the aggregation level. But the fact table of the InfoCube does not contain A__B since one can get the value of A__B always using a join to the master data table.

In this sense a navigation attribute is completely redundant and thus 'planning on a navigation attribute' has no real meaning. You can just use the navigation attribute e.g. to filter by attribute values.

Whether it is reasonable to add the characteristic B to the InfoCube depends on the scenario; using such a design would allow to store combinations of A,B that don't exist in the master data table of A. One can ensure that only combinations (a,b) of characteristic values from A,B contained in the master data table of A are allowed using a characteristic relationship based on master data table of A.

Regards,

Gregor