Analyzing and fixing authorization errors for SPRO transactions in Cloud

[former_member382758]

Often we face the authorization error ‘You are not authorized to use transaction….’ or ‘You do not have authorization to change the data (display only)’ while trying to launch SPRO transactions in cloud systems.

Now the common question comes up: ‘How to analyze and resolve this error?’ for developers who are not familiar with the authorization topic.

Let us go through an example of how to troubleshoot and fix the authorization issue.

Launch the transaction from backend system or open the app in frontend.

You will see an error as ‘You are not authorized to use transaction….’ or ‘You do not have authorization to change the data (display only)’.

Launch transaction SU53 in backend system. By default, the screen displays the list of failed authorizations for the backend user. Use the Display for different user button for changing the user. (If app was opened from frontend, check failed authorizations for the corresponding CBXXXXXXXX user.)

The failed authorizations will be listed as given below:

Check for the missing authorization for the transaction which was launched earlier. Usually, the errors will be due to missing values for authorization object S_TABU_NAM.

Launch SU22 transaction for the SPRO tcode in the development system. Click on Execute button.

The Proposal for authorization object S_TABU_NAM should be ‘Yes’ and the missing values listed in SU53 needs to be maintained in field S_TABU_NAM-TABLE.

This method of troubleshooting the errors has reduced the headache of debugging every authorization check performed while executing SPRO transactions in Cloud.