How To Fix /PICM/UI120 - You are not authorized to edit change requests

SAP Error Message - Details

• Message type: E = Error

• Message class: /PICM/UI -

• Message number: 120

• Message text: You are not authorized to edit change requests

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 /PICM/UI120 - You are not authorized to edit change requests ?

  The SAP error message /PICM/UI120 You are not authorized to edit change requests typically indicates that the user does not have the necessary authorizations to edit change requests in the SAP system. This can occur in various SAP modules, particularly in the context of change management or project management.
  Cause:
  
  Authorization Issues: The user lacks the required authorization roles or permissions to edit change requests.
  Role Assignment: The user may not have been assigned the correct roles that include the necessary authorizations for change request editing.
  Profile Restrictions: The user’s profile may have restrictions that prevent editing of certain objects or transactions.
  System Configuration: There may be specific configurations in the system that restrict access based on certain criteria.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and check the roles assigned to the user.
  Ensure that the user has the necessary roles that include permissions for editing change requests.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after encountering the error to see which authorization objects are missing.
  Common authorization objects related to change requests include S_CRM_ACTIVITY, S_CRM_ORDER, and others depending on the specific context.
  
  
  
  Request Additional Authorizations:
  
  If the user does not have the required roles, contact your SAP security team or administrator to request the necessary authorizations.
  Provide them with the details of the error message and the context in which it occurred.
  
  
  
  Check for Profile Restrictions:
  
  Review the user’s profile for any restrictions that may prevent editing change requests.
  Adjust the profile settings if necessary.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or your organization’s internal guidelines for managing authorizations and roles.
  
  
  
  Testing:
  
  After changes are made, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the functionality to confirm that the user can now edit change requests.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  SAP Notes: Check SAP Notes for any known issues or updates related to authorization errors in your specific version of SAP.
  
  
  Documentation: Review the SAP Help Portal for detailed information on authorization management and best practices.
  
  
  If the issue persists after following these steps, it may be necessary to involve your SAP Basis or security team for further investigation.