How To Fix /PICM/UI093 - No authorization to change activity to status '&1' for activity type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /PICM/UI -

• Message number: 093

• Message text: No authorization to change activity to status '&1' for activity type &2

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/UI093 - No authorization to change activity to status '&1' for activity type &2 ?

  The SAP error message /PICM/UI093 No authorization to change activity to status '&1' for activity type &2 typically indicates that a user is attempting to change the status of an activity in the Project Management module (or a related module) but does not have the necessary authorizations to perform that action.
  Cause:
  
  Authorization Issues: The user lacks the required authorization object to change the status of the specified activity type. This could be due to missing roles or authorizations in their user profile.
  Activity Type Restrictions: Certain activity types may have specific restrictions or require additional permissions to modify their status.
  Configuration Settings: The system may have been configured to restrict status changes based on user roles or project settings.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user's roles and authorizations in transaction PFCG to ensure they have the necessary permissions for the activity type in question.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, you may need to add the required roles or adjust existing roles to include the necessary authorization objects (e.g., C_PROJ for project management).
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes to user roles, contact your SAP security team or administrator to request the necessary authorizations.
  
  
  
  Review Activity Type Settings:
  
  Check if there are any specific settings or restrictions for the activity type that might be preventing the status change. This can be done in the project management configuration settings.
  
  
  
  Testing:
  
  After making changes to authorizations or roles, have the user log out and log back in to ensure that the new permissions take effect. Then, attempt the status change again.
  
  
  
  Related Information:
  
  Authorization Objects: Common authorization objects related to project management include C_PROJ (Project Management) and C_PRC (Project Control).
  Transaction Codes:
  
  SU53: Display authorization check.
  PFCG: Role maintenance.
  SE93: Transaction codes and authorization checks.
  
  
  Documentation: Refer to SAP Help documentation for detailed information on authorization management and project management configurations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve the authorization issue.