How To Fix SU22TODO121 - Report &1: You are not authorized to send system messages

SAP Error Message - Details

• Message type: E = Error

• Message class: SU22TODO - T100 Messages for ToDo SU22

• Message number: 121

• Message text: Report &1: You are not authorized to send system messages

What causes this issue?

The user that executed report &1 is not authorized to send system
messages.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

To send system messages, you require an authorization for the
object S_ADMI_FCD with the value 'SM02' in the field 'S_ADMI_FCD'.
Contact your system administrator to request this authorization.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SU22TODO121 - Report &1: You are not authorized to send system messages ?

  The SAP error message SU22TODO121, which states "Report &1: You are not authorized to send system messages," typically indicates that the user does not have the necessary authorizations to send system messages in the SAP environment. This can occur in various scenarios, such as when trying to execute a report or transaction that involves sending messages to users or system logs.
  Cause:
  
  Authorization Issues: The user lacks the required authorization object to send system messages. This is often related to the authorization object S_USER_AUTH or other relevant authorization objects that control message sending capabilities.
  Role Configuration: The user's role may not include the necessary permissions to execute the specific report or transaction that attempts to send system messages.
  System Settings: There may be system-wide settings or configurations that restrict message sending capabilities for certain users or roles.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization is missing.
  Review the user's roles and profiles in transaction SU01 or PFCG to ensure that the necessary authorizations are included.
  
  
  
  Modify Roles:
  
  If the required authorizations are missing, you may need to modify the user's roles or create a new role that includes the necessary authorizations for sending system messages.
  Ensure that the role includes the relevant authorization objects, such as S_USER_AUTH, and any other specific objects related to the report or transaction.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to modify roles or authorizations, consult with your SAP security team or administrator. They can help identify the missing authorizations and make the necessary adjustments.
  
  
  
  Testing:
  
  After making changes to the roles or authorizations, have the user log out and log back in to ensure that the new permissions take effect. Then, attempt to execute the report or transaction again.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SU53: Display Authorization Check
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control message sending capabilities, such as S_USER_AUTH.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on authorization issues.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message SU22TODO121.