How To Fix NSDM_MESSAGES035 - No authorization for &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: NSDM_MESSAGES - Messages MM-IM new simplified data model

• Message number: 035

• Message text: No authorization for &1 &2 &3

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 NSDM_MESSAGES035 - No authorization for &1 &2 &3 ?

  The SAP error message NSDM_MESSAGES035 indicates that a user does not have the necessary authorization to perform a specific action or access certain data. The placeholders &1, &2, and &3 typically represent the object type, the action, and the specific data or context related to the authorization check.
  Cause
  The error is usually caused by one of the following reasons:
  
  Missing Authorizations: The user does not have the required authorizations assigned in their user profile for the specific action they are trying to perform.
  Role Issues: The roles assigned to the user may not include the necessary authorizations for the transaction or data access.
  Authorization Object Restrictions: The authorization objects that govern access to the specific transaction or data may have restrictions that the user does not meet.
  Profile Changes: Recent changes to user roles or profiles may have inadvertently removed necessary authorizations.
  
  Solution
  To resolve the error, you can follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs. This will show you the last authorization check and help identify which specific authorization is missing.
  Alternatively, you can use transaction SU01 to view the user’s profile and roles.
  
  
  
  Review Roles and Authorizations:
  
  Check the roles assigned to the user in transaction PFCG. Ensure that the roles include the necessary authorizations for the action being attempted.
  If the roles are missing the required authorizations, you may need to modify the role or create a new one that includes the necessary permissions.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to make changes, contact your SAP security team or administrator. Provide them with the details of the error and the actions you were trying to perform.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, have the user log out and log back in to ensure that the changes take effect. Test the action again to confirm that the issue is resolved.
  
  
  
  Related Information
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that govern the specific transaction or data access. You can find this information in the SAP documentation or by consulting with your security team.
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization errors.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the NSDM_MESSAGES035 error.