Skip to Content

SQL AP doesn't work with multiple views with restriction fields that are not common to all views

Hi all,

I am trying to migrate a classical analytic privilege (AP) to SQL AP. My classical AP has

multiple calculation views CV_Sales_Overview and CV_Product_Overview and the restrictions are as follows:

Restriction on CV_Sales_Overview = SALES_COUNTRY='INDIA'

Restriction on CV_Product_Overview = PRODUCT_TYPE='P1-1100'

The above two restrictions with different fields are added to the same AP(classical AP).

If I try to simulate the same AP(manually) using an SQL AP I cannot do it because the SQL AP activation fails with error: Invalid column name. This is because the SQL AP applies the entire restrictions to all the calculation views and since the PRODUCT_TYPE field is not in CV_Sales_Overview the activation fails.

This is strange the way SQL AP works as compared to Classical APs. There must be a provision there to add multiple views in the an SQL AP with attributes which are not common to all the views and should consider only the restriction attributes of the corresponding view while applying the restriction. Please find a solution or fix for this problem.

I cannot split the Classical APs to SQL AP per calculation view because I have so many views added in the Classical AP and there are so many such Classical APs to be converted to SQL AP. This will be a huge task to achieve.

Also I cannot use the migration tool provided by SAP as all my Classical APs have a procedure as a restriction.

Please help me with a working solution for the above problem.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers