SAC PLANNING - how to build a set of non related dimension combination in a table

[former_member767054]

Hi everybody.

I have more experience on BPC and in the EPM addin I would have adressed this topic by "playing" with the EPMOlapMember formulas (referencing some hidden columns providing the combinations), but I don't think there is something similar to be done in SAC Planning.

Here is the requirement :

I have to provide tables in stories with a set of particular combinations among 3 dimensions : account, cost centers and activities. For example :

Activity_A / ACCOUNT_A / CC_A

Activity_A / ACCOUNT_B / CC_A

Activity_A / ACCOUNT_C / CC_A

Activity_A / ACCOUNT_C / CC_A

Activity_A / ACCOUNT_C / CC_B

Activity_B / ACCOUNT_D / CC_D

There is no logic in the way combinations could be generated automatically (100% business knowledge).

If I just perform some filters on those 3 dimensions, I'll have all the possible "tuples" of all members.

Is there a way to build something more clever than just build the full set of combinations, and then hide the ones we don't need ?

There's kind of a track here, but this is working with 2 dimensions, and limited because of the property size :

https://blogs.sap.com/2020/05/14/dimension-combination-rule-in-sac/

Thanks in advance for sharing your knowledge, and regards.

G.

[former_member767054 · Accepted solution]

Hi Jay.

Thanks for the feedback.

Yes, among the 3 dimensions there is the one which is account-typed. Looks like the type "account" for a dimension is bringing lot of complexity (I'm struggling with a cascading filter topic, and once again the account-typed dimension is my issue).

Your workaround is interesting. We could with minimum effort upload "1" values at all relevant crossings, and final users would just have to replace those "1"s with the real planned figures.

Do you have maybe in mind an idea to post the "flag value" into a matrix that would not be visible (with "1"s everywhere) ?

Thanks again.

G.

[Jay_Gandhi]

Hi there,

You could use advanced filters, however, in your example if you're using the Account-type dimension it is not supported to define them for asymmetric purposes.

A workaround you could use is to first populate data in the valid combinations and/or a flag of some sort with either manual entry or data actions and then only display "booked values" so that only the combinations you'd like to view are displayed.

Jay