How To Fix EYE050 - Aggregation authorization must be assigned for characteristic &1

EYE050 - Overview

• Message type: E = Error

• Message class: EYE - Messages in queries for analysis authorizations

• Message number: 050

• Message text: Aggregation authorization must be assigned for characteristic &1

What causes this issue?

Characteristics that do not occur in the drilldown but that exist in the
InfoProvider are always aggregated. The displayed transaction data is
always displayed as aggregated using these characteristics.
If this type of aggregated characteristic is authorization-relevant, at
least one aggregation authorization must be assigned for this
characteristic. (This can also be represented by full authorization (*)
for the characteristics, if this is supported.)

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Consider this requirement when assigning authorizations to users who
execute queries.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

EYE050 - Details

• The SAP error message EYE050 indicates that there is an issue with aggregation authorization for a specific characteristic in your SAP system. This error typically arises in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when a user attempts to access data that requires specific authorization for aggregation.
  
  Cause:
  The error occurs when:
  
  A user tries to execute a query or report that involves aggregating data based on a characteristic for which they do not have the necessary authorization.
  The characteristic in question is not assigned the required aggregation authorization in the authorization object.
  
  
  Solution:
  To resolve the EYE050 error, you can follow these steps:
  
  
  Check User Authorizations:
  
  Verify the user's roles and authorizations in the SAP system. Ensure that the user has the necessary permissions to access the characteristic in question.
  
  
  
  Assign Aggregation Authorization:
  
  Go to the transaction code PFCG (Role Maintenance).
  Find the role assigned to the user and check the authorization objects related to