Hi,
I suggest a different approach. Colon / aggregation authorization can be considered as a best practice to avoid "unexpected" authorization issues. It is checked if the characteristic is in the free characteristics (not in drilldown) without any selections or the characteristic does not exist in the BEx Query at all (but is authorization-relevant and part of the InfoProvider).
In my opinion you should create a variable "filled by authorization" and add it to the global filter (i.e. characteristic restrictions) of the BEx Query. This will overrule the colon / aggregation authorization to be checked. The BEx Query global selection will automatically be restricted to the authorized values.
Please refer to the following SAP Notes for more information:
- SAP Note 1140831 - Colon authorization during query execution;
- SAP Note 1904962 - How to Analyze a "No Authorization" or Showing Too Much Data Issue with BW Analysis Authorization.
Best regards,
Sander