Filter a dimension based on Property of another dimension

[kvsreekar]

Hi Friends,

I have a requirement where I need to display only a desired combination of Dimension Members in the Planning Layout/Story.

I am trying to control it based on the Property of one dimension reading the Member ID of another dimension.

In the below example: I have a list of Services I need to display for User Input but those Services are only valid for a certain Section. I don't want the user to manually select the Correct Section in input controls (because there are a lot of Services & Section combos), instead I want the correct Section to Automatically be displayed next to the Service based on the Section Property I defined on the Service Dimension. See below screenshot.

I have Service root as 'Input Control' in the story. In

Below is the screenshot of the SECTION Dimension. I'm using the Base member as the property value in the above SERVICE dimension.

The Planning Layout should look like in the below screenshot:

I don't want to display all the combination of Sections & Services as shown in the below screenshot:

I tried Advanced Filtering but it doesn't have the ability to compare a dimension member ID with the Property value of another dimension member.

If it makes it easy I can add a Input Control for Service where the users can select a Service Hierarchy Node (ex SN03) and we can at least derive the SECTION Filter value based on this input control.

[N1kh1l · Accepted solution]

kvsreekar

Currently its not possible to show dimension based on attributes of another dimension. There is a request for considering this feature which you can vote below. As a work around, use a Data Action to initialize these member combination with a value "1" on an appropriate intersection and then uncheck the Show booked option on the table for that dimension.

Improvement Request Details - Customer Influence (sap.com)

Please upvote/accept if this helps.

Regards

Nikhil

[kvsreekar · Accepted solution]

Thanks nikhil_1486

Yes, I eventually ended up using the approach you suggested only. i.e. post dummy transactions flagging the required member combinations and hide that column on the layout.

Disappointment after disappointment from SAC.

[MKreitlein]

Hello Sreekar,

what you found out and Nikhil describes is unfortunately a behaviour which exists quite long and SAP implemented only EITHER all combinations OR only the ones with values 😞

Besides that, I found out another "bug" lately... even if you can use properties for filtering, the commenting option on data cells is not available anymore 😞

Only Dimension filters enable commenting on cell-level.

It might be not directly related to your topic... but here you can see some side effects on a rather little issue 😉

BR, Martin

[kvsreekar]

Yes, data point commenting is another issue we have when using property based filters.

Similarly we have a gazillion issues to fix and huge room of improvements in SAC. I hope SAP don't take till year 2025 to fix all these issues and once they do they might dump the product and start something new (may be SAP Quantum Computing on Cloud) with no legs and hands and expect the consultant to deliver to their customers.

[MKreitlein]

Sad but true 😞 ... this is software developement in the 21st century.