How To Fix SRT_MONITORING035 - User '&1' does not have authorization to delete payload trace

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_MONITORING - Message Class for SOAP Runtime Monitoring

• Message number: 035

• Message text: User '&1' does not have authorization to delete payload trace

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 SRT_MONITORING035 - User '&1' does not have authorization to delete payload trace ?

  The SAP error message SRT_MONITORING035 indicates that a user is attempting to delete a payload trace in the SAP system but does not have the necessary authorization to perform this action. This error typically occurs in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO) when dealing with monitoring and managing message traces.
  Cause:
  The primary cause of this error is a lack of appropriate authorization for the user attempting to delete the payload trace. In SAP, user authorizations are managed through roles and profiles, and specific permissions are required to perform certain actions, such as deleting traces.
  Solution:
  To resolve this issue, you need to ensure that the user has the necessary authorizations. Here are the steps to do that:
  
  
  Identify the User: Determine which user is encountering the error.
  
  
  Check User Roles: Review the roles assigned to the user. You can do this by using transaction code SU01 (User Maintenance) to view the user's profile.
  
  
  Assign Necessary Authorizations:
  
  The user needs to have the appropriate authorization object for deleting payload traces. The relevant authorization object is typically S_SRT_MONI.
  Ensure that the user has the following authorizations:
  
  Activity: The user should have the activity for deleting traces (usually 02 for delete).
  Object: The user should have access to the relevant service or interface.
  
  
  
  
  
  Modify Roles: If the user does not have the necessary authorizations, you may need to modify their roles or create a new role that includes the required authorizations. This can be done using transaction code PFCG (Role Maintenance).
  
  
  Test the Changes: After updating the roles, have the user log out and log back in to ensure that the changes take effect. Then, test to see if the user can now delete the payload trace without encountering the error.
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects and their fields. You can use transaction code SU21 to find more information about authorization objects.
  Audit Logs: If you need to track changes or access issues, consider checking the audit logs for any unauthorized access attempts.
  Documentation: Refer to SAP documentation for more details on user authorizations and role management in your specific version of SAP.
  
  By following these steps, you should be able to resolve the authorization issue and allow the user to delete payload traces successfully.