Quantcast
Channel: SCN : Discussion List - SAP Planning and Consolidation, version for SAP NetWeaver
Viewing all articles
Browse latest Browse all 5414

Question: Dimension Design on Compounded Property/Attribute.

$
0
0

Hi All -

 

Good day to you all,

 

I would kindly like to kindly ask your thought with regards to the best practice on Compounded Attribute/Property in Dimension.

 

For e.g. I have Cost Centre Dimension - (User Defined). Member of Cost Center has dependency to Controlling Area. The reason is 1 same cost center number can be owned by 2 different Controlling Area. Hence, we need to have controlling area values in Cost Center Dimension to differentiate it.

 

If I read to SDN that I need to CONCATENATE :

ID = Co.Area + Cont Center

 

Hence, Cost Center Dimension member will be:

 

ID
CA011000001
CA011000002
CA021000002
CA021000001

 

NB:

CA01, CA02 = Controlling Area

1000001, 1000002 = Cost Center

 

The Questions are

1) Is it the best practice in BPC? How typically all of you handle the case for member of dimension whereby the Primary keys need more than one (Compounded Attribute)?

Do you use "CONCATENATE" to ID? Or if you have the different way, kindly please share your thought.

 

2) If we use "CONCATENATE", how's the approach business to enter value in BPC Input Form? Do they needs to key Controlling Area + Cost Center ? Is it commons ?

 

Thanks in advance,

 

Appreciate it much for your help,

 

Look forward to your guidance,

 

Cheers,


Viewing all articles
Browse latest Browse all 5414

Trending Articles