cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Filter Variable on Fields with Compound Keys

maffio
Explorer
0 Kudos
221

Hello Expert.

Let us assume to have an Analytical Model in Sap Datasphere and to want to create a Filter Variable on a Field of the Analytical Model, where the Field has Compound Keys. My question is: how does the Filter Variable behave with respect to the Compound keys? As far as I see, it looses the compouding fields and all the related information (such as texts); besides, if it looses the compounding fields, on a matter of fact, I don't know how it applies the filter in the Analytical Model.

View Entire Topic
Martin_Kuma
Contributor
0 Kudos

Hi, let's say you have in you model-view (FACT-view) G/L Account and Chart Of Accounts fields. Compounded keys.

In the AM you create one Filter Variable for G/L Account, the AM will filter the selected G/L Account/s regardless of Chart of Accounts. 

In the AM you create second Variable for the Chart of Accounts, AM will filter all G/L Accounts belonging to the one Chart of Account. 

If you use both variables, you will get the expected result. Means compounded key as you know from BW is not used in DSP. 

Even if you use parameters passed from model-view passed to AM. Same for associations. 

 

 

maffio
Explorer
0 Kudos
Hello Martin. Thanks for your reply. Yes, I agree with you, but, you will agree with me, this does not solve the issue if not partially. If you loose the compouding, then you will loose the descriptions of the field. And presenting to a business user IDs instead of descriptions is not a great job! I am pretty much sure that he will open a ticket pointing out the anomaly. Thanks in any case for your feedbacks, I appreciated them a lot
Martin_Kuma
Contributor
0 Kudos

I missed the description detail, sorry :(. With Account it is easy as the accounts tend to have the same description across chart of accounts. I had similar issue with cost elements / controlling area. Two possibilities

#concat key --> ugly in the front-end

#parameter for the upper level key in the Assoc. You pass the parameter from model/FACT-View to the Assoc. Consume the parameter in AM via variable (value passed from SAC). 

Disadvantage is with the parameters self as it will be mandatory. You also will need to decide if the user is to enter any value, or you do it in the background -> additional scripting. But this will work.