How To Fix SRM_REGISTRY120 - No authorization

SRM_REGISTRY120 - Overview

• Message type: E = Error

• Message class: SRM_REGISTRY - Registry Maintenance

• Message number: 120

• Message text: No authorization

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 SRM_REGISTRY120 - No authorization ?

  The SAP error message SRM_REGISTRY120 indicates that a user does not have the necessary authorization to perform a specific action within the SAP Supplier Relationship Management (SRM) system. This error typically arises when a user attempts to access a function or transaction for which they lack the required permissions.
  
  Cause:
  
  Missing Authorizations: The user’s role does not include the necessary authorizations for the action they are trying to perform.
  Role Assignment Issues: The user may not be assigned the correct role or profile that includes the required authorizations.
  Authorization Object Restrictions: Specific authorization objects may be restricting access based on organizational levels, such as company codes, purchasing organizations, or other criteria.
  Changes in Authorization Profiles: Recent changes to authorization profiles or roles may have inadvertently removed necessary permissions.
  
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction code SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the necessary roles that include