cancel
Showing results for 
Search instead for 
Did you mean: 

Has anyone created a BPC hierarchy for the version dimension to assist in organizing & viewing them?

lisa_savinovich
Active Participant
482

Dear SCN Members,

We have a great deal of versions (80) in BPC 10.1 NetWeaver. Has anyone ever created a version dimension hierarchy to group together the key versions and have the node with them display first? I realize this is an odd question in that we do not want to summarize the data in these various versions.

Thank you,

Lisa

Accepted Solutions (1)

Accepted Solutions (1)

N1kh1l
Active Contributor
0 Kudos

lisa.savinovich

If you want to just show 20 of them in an ordered way in member selector console in report and forms, just create the hierarchy and do not assign any parent (blank parent h1 column) . Then go to Hierarchy view in category dimension and arrange the 20 key version members in the top 20 order by moving up and down. Save and process the dimension once list is ordered.

I have arranged Plan, Budget and Forecast as top 3

Before it used to show up in alphabetic order so all Actuals were on top

Hope this helps !! You will achieve an orderly listing and no fear of any parent member

Br.

Nikhil

lisa_savinovich
Active Participant
0 Kudos

Hi Nikhil,

This sounds like perfect approach! Thanks again for your timely response.

Sincerely,

Lisa

Answers (1)

Answers (1)

N1kh1l
Active Contributor
0 Kudos

lisa.savinovich

Technically you can create a hierarchy in category dimension and use a parent node to group all versions but as you said this is functionally a weird requirement as very rarely one aggregates versions. Also 80 versions is very rare, generally we use other dimensions to split data in conjunction with version. What you have to note is below

  • If the parent node is shown in any report or form, it will show aggregated sum of versions it is parent of.

Br.

Nikhil

lisa_savinovich
Active Participant
0 Kudos

Hi Nikhil,

Yes, it is an odd use of a hierarchy. And the number of versions that we have is driving the inquiry about this odd use of hierarchies. Is there a way to organize member data that does not have hierarchies? Within our versions, there are probably around 20 that are key that we would prefer to show at the top of the list of dimension members when one is looking for a version.

Thank you for reply.

Sincerely,

Lisa