How To Fix RSM1649 - Success messages are NOT written to the SM37 job log

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 649

• Message text: Success messages are NOT written to the SM37 job log

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 RSM1649 - Success messages are NOT written to the SM37 job log ?

  The SAP error message RSM1649 indicates that success messages are not being written to the job log of a background job in transaction SM37. This can be a concern for users who want to track the successful execution of background jobs.
  Cause:
  The primary cause of this error message is that the job log is configured to only capture error messages and not success messages. By default, SAP background jobs may not log success messages to avoid cluttering the job log with information that is not critical for monitoring job execution.
  Solution:
  To address this issue, you can take the following steps:
  
  
  Check Job Log Settings: Ensure that the job log settings are configured to capture success messages. You can do this by checking the job's configuration in transaction SM37.
  
  
  Modify Job Log Behavior:
  
  If you want to see success messages in the job log, you may need to adjust the job's settings or the program that is being executed. This may involve modifying the ABAP code to explicitly write success messages to the job log using the WRITE statement or using the function module RS_LOG_WRITE.
  You can also use the MESSAGE statement in ABAP to log messages with the appropriate severity level (e.g., I for information).
  
  
  
  Review Job Execution: After making changes, re-execute the job and check the job log again in SM37 to see if the success messages are now being recorded.
  
  
  Consult Documentation: If you are unsure about how to modify the job log settings or the ABAP code, refer to the SAP documentation or consult with your SAP Basis or ABAP development team for assistance.
  
  
  Related Information:
  
  Transaction SM37: This transaction is used to monitor background jobs in SAP. You can view job status, logs, and details about job execution.
  Job Log: The job log provides information about the execution of background jobs, including any messages generated during the job's runtime.
  ABAP Programming: If you are a developer, understanding how to use the MESSAGE and WRITE statements in ABAP can help you control what gets logged during job execution.
  
  By following these steps, you should be able to resolve the issue of success messages not being written to the job log in SAP.