Re: Question: Dimension Design on Compounded Property/Attribute.

Hi Vadim -

Thanks you very much for feedback on this design question, appreciate it much.

Vadim Kalinin wrote:

 

Hi Naomi,

 

The BPC dimension structure depends on planning and reporting business requirements. Ask business, what do they wont or able to plan and what reports to have...

 

In some cases Controlling area can be a dimension, in some cases concatenation approach can work, or even aggregate cost center without controlling area...

 

Vadim

These are the business requirements:

• Business wants to plan on their own cost centre (according to their Controlling Area).

       We don't have cost centre hierarchy to segment it based on controlling area.

• Beside business, they're also super user who can do planning, and this super user handle more than one controlling area data.
• This BPC planning application will be set as planning application template. Hence, it will be used by many regions and controlling area.

For this requirement, I'm planning to

1. Creating Controlling Area as user Defined and make it as Security dimension in the model. In Input planning form, Business needs to key in the variable selection screen on controlling area to discern their data plan. Business also will be only able to plan on their own controlling area, except for super user, they will be able to do a planning to more than one Controlling Area.
2. For Cost centre ( I still have a confuse ).
   • The type is: User define.
   • I'm thinking to use Concatenation to differentiate this cost centre belong to controlling area A and B. However, since business has already input variable screen : controlling area in their planing form.
     • Do you think that it is redundancy for  business to key in Concatenation: Co. Area + Cost Centre? The reason is because Input Planning Form has already had separate Controlling Area Variable Selection Screen that business needs to key in.

The Questions:

1. Is my design BPC Planning correct especially to address the cost center design whereby cost center has a dependency to Controlling area?

How do you typically design for the dimension that the member has a dependency. In SAP BW, we have luxury to have compounded attribute in one Info Object, however, I am not sure how we can do it in BPC.

2. How to solve the issue on redundancy for business to key in controlling area: Cost centre dimension: co.area + cost centre?

Business will think that since they have already key in separate controlling area variable selection screen, they will think this cost centre should capture the one owned by its controlling area.

3. I am interested on your feedback on Aggregate of Cost Center without Controlling Area. Would you mind explaining more on this one?

Looking forward to your thought on this, and appreciate much.

Thanks in advance,

Cheers,