How To Fix /SEHS/DG_DG605 - You do not have authorization to edit &1, &2, &3, &4

SAP Error Message - Details

• Message type: E = Error

• Message class: /SEHS/DG_DG -

• Message number: 605

• Message text: You do not have authorization to edit &1, &2, &3, &4

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SEHS/DG_DG605 - You do not have authorization to edit &1, &2, &3, &4 ?

  The SAP error message /SEHS/DG_DG605 indicates that a user does not have the necessary authorization to edit specific objects or entries in the system. This error typically arises in the context of SAP's Data Governance or similar modules where user permissions are strictly enforced.
  Cause:
  The error is caused by insufficient authorization for the user attempting to perform an edit operation on the specified objects (indicated by &1, &2, &3, &4). This can happen due to several reasons:
  
  Missing Authorization Roles: The user may not have been assigned the appropriate roles that grant edit permissions for the specific objects.
  Authorization Object Restrictions: The authorization objects related to the editing function may not be properly configured for the user.
  Profile Issues: The user profile may not include the necessary permissions to perform the action.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that they include the necessary permissions for editing the specified objects.
  
  
  
  Review Authorization Objects:
  
  Identify the relevant authorization objects that control access to the editing function. This can often be found in the documentation or by consulting with your SAP security team.
  Use transaction SU53 immediately after the error occurs to see which authorization checks failed. This will provide insight into what specific permissions are lacking.
  
  
  
  Modify Roles:
  
  If the user lacks the necessary roles, work with your SAP security administrator to assign the appropriate roles or modify existing roles to include the required permissions.
  
  
  
  Testing:
  
  After making changes to the user roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
  Attempt the edit operation again to verify that the issue has been resolved.
  
  
  
  Documentation and Training:
  
  Ensure that users are aware of the permissions required for their tasks and provide training if necessary to prevent similar issues in the future.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  SU53 - Display Authorization Check
  PFCG - Role Maintenance
  
  
  Authorization Objects: Common authorization objects related to editing in SAP include S_TCODE, S_USER_AUTH, and others specific to the module in use.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide guidance on authorization management.
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.