How To Fix SRM_REGISTRY120 - No authorization

SAP Error Message - Details

• 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 the required authorizations are assigned.
  
  
  
  Review Authorization Objects:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization objects are missing.
  This will provide insight into what specific authorizations need to be granted.
  
  
  
  Modify Roles:
  
  If you have the necessary permissions, you can modify the roles using transaction code PFCG (Role Maintenance).
  Add the required authorization objects to the relevant roles.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to make changes, contact your SAP security or basis team to review and adjust the user’s authorizations.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the functionality again to confirm that the error has been resolved.
  
  
  
  Related Information:
  
  Authorization Concept in SAP: Understanding how authorizations work in SAP is crucial. Authorizations are managed through roles and profiles, which define what actions users can perform within the system.
  Documentation: Refer to SAP documentation or the SAP Help Portal for detailed information on authorization objects related to SRM.
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to SRM authorizations.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the SRM_REGISTRY120 error.