Significance of Dimension in MPOS

[Former Member]

Hi all,

We can create MPOS using Tcode /SAPAPO/MSDP_ADMIN.

Here we create POS using existing Characteristics.

There is a field called "Dimension", we have to assign to each Characteristic.

Usually the value for Dimension is 1.

Qus :- (1) What is the significance of Dimension ?

(2) What can be the possible values for Dimension ?

(2) In which scenario its value can be 1 or 2 or etc. ?

Thanks,

Debi

[former_member698542]

HI Debi,

The planning object structure which supports the planning area is nothing but like a info cube in BW.

The BW helps to store data in Multi Dimensional tables. The Dimension is nothing but the combination of characteristics. For example I want to have a Dimension called Product. The this dimension PRODUCT can have characteristics like Product hierarchy,product group,product number etc. The another dimension named Organization or (Sales) may have characteristics like Sales organization, Distribution channel, Division etc.

Basically the Dimension helps for data analysis the key figure data and reporting the key figures based on the characteristics (dimensions). The aggregation and disaggregation of key figure data is stored on the basis of dimensions.

So you will enter Dimension 1 for all PRODUCT related characteristics, Dimension 2 for all Organization related characteristics.

thanks and regards

Murugesan

[Former Member]

Thanks Murugesan for your input.

Please answer my qus :-

Say, the MPOS has 6 No. of characteristics out of 3 are linked to dimension Product and the rest 3 are linked to dimension Location.

Ideally the 3 characteristics linked to Product should have dimension as 1 and the rest 3 characteristics linked to Location should have dimension 2.

But many cases I have observed that the dimesion is kept as 1 for all characteristics in /SAPAPO/MSDP_ADMIN tcode even though they belong to different dimensions.

I think this is wrong. Please comment.

Thanks,

Debi

[Former Member]

Hi Debi,

You are correct from core BW point of view. But the real use of dimensions is efficient data storage, retrieval and reporting. We don't need any of these functions with the MPOS, even thought it's also a cube. So, to be correct, yes we need to assign structurally different characteristics to different dimensions but they are not that important in case of these MPOS and APO context.

[Former Member]

Thanks Visu