How To Fix /SCWM/SYS_DOC_MON058 - You are not authorized to use transaction &1 in system &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/SYS_DOC_MON -

• Message number: 058

• Message text: You are not authorized to use transaction &1 in system &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 /SCWM/SYS_DOC_MON058 - You are not authorized to use transaction &1 in system &2 ?

  The SAP error message /SCWM/SYS_DOC_MON058 indicates that a user is attempting to access a transaction for which they do not have the necessary authorization. This is a common issue in SAP systems, particularly in environments with strict security and role-based access controls.
  
  Cause:
  The error occurs when:
  
  The user does not have the required authorization object assigned to their user profile.
  The transaction code (&1) being accessed is restricted based on the user's role or profile.
  The system (&2) may have specific authorization checks that are not met by the user's current settings.
  
  
  Solution:
  To resolve this issue, follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction SU53 immediately after the error occurs. This transaction will show you the last authorization check that failed, which can help identify the missing authorization object.
  
  
  
  Review User Roles:
  
  Go to transaction SU01 and enter the user ID to check the roles assigned to the user.
  Ensure that the user has the necessary roles that include the