SM21 - system log

SAP Transaction Code - Details

• Transaction Code: SM21

  Description: system log

  Release: S/4HANA and ECC 6

  Menu Path:

  • Tools > ABAP Workbench > Test > System Log
  • Tools > Administration > Monitor > Performance > Exceptions/Users > Exceptions > System Log
  • Tools > Administration > Monitor > System Log
  • Tools > CCMS > Control/Monitoring > Performance > Exceptions/Users > Exceptions > System Log

• • Program: RSYSLOG

    Screen: 1000

    Authorization Object:

  • Development Package: SYSLOG

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: SM21 - system log

  
  Overview:
  The SAP transaction code SM21 is used to view the system log. This log contains information about system events, such as errors, warnings, and other messages. It is a useful tool for troubleshooting and monitoring system performance. 
  
  Functionality: 
  The SM21 transaction code allows users to view the system log in real-time. It displays all messages that have been logged in the system, including errors, warnings, and other information. The log can be filtered by date, time, user, and message type. This makes it easy to find specific messages or events that have occurred in the system. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code SM21 in the command field. 
  2. Select the date range for which you want to view the log. 
  3. Select any additional filters you want to apply (e.g., user, message type). 
  4. Click “Execute” to view the log entries that match your criteria. 
  5. To view more details about a particular entry, double-click on it. 
  6. To save the log entries to a file, click “Save” and select a file format (e.g., CSV). 
  7. To exit the transaction code, click “Back” or “Cancel”. 
  
  Other Recommendations: 
  It is recommended that users regularly check the system log for any errors or warnings that may indicate a problem with the system or its performance. Additionally, users should save the log entries periodically in order to track changes over time and identify any potential issues that may arise in the future.