How To Fix RT_EN072 - Job successfully scheduled.

SAP Error Message - Details

• Message type: E = Error

• Message class: RT_EN - Monitoring Infrastructure alerts and texts; English origin

• Message number: 072

• Message text: Job successfully scheduled.

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 RT_EN072 - Job successfully scheduled. ?

  The SAP error message RT_EN072 ("Job successfully scheduled") is not actually an error in the traditional sense; rather, it is an informational message indicating that a background job has been successfully scheduled in the SAP system. This message typically appears in the context of job scheduling using transaction codes like SM36 (Define Background Job) or SM37 (Job Monitoring).
  Cause:
  
  The message is generated when a user schedules a background job, and the system confirms that the job has been successfully added to the job queue for processing.
  
  Solution:
  Since RT_EN072 is an informational message, there is no "solution" required in the sense of fixing an error. However, if you are looking to verify or manage the scheduled job, you can do the following:
  
  
  Check Job Status: Use transaction code SM37 to monitor the status of the scheduled job. You can filter by job name, user, or date to find the specific job you scheduled.
  
  
  Review Job Logs: After the job has run, you can check the job log for any messages or errors that may have occurred during execution. This can help you understand the outcome of the job.
  
  
  Modify Job Settings: If you need to change the job parameters (like the frequency, start time, or variant), you can do so in transaction SM36 or by selecting the job in SM37 and choosing to change it.
  
  
  Delete or Cancel Job: If you need to cancel or delete the job, you can do this from the SM37 transaction as well.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM36: Define Background Job
  SM37: Job Monitoring
  SM21: System Log (to check for any system-related issues)
  
  
  
  Job Types: Background jobs can be of various types, including ABAP programs, external commands, or other tasks that need to be executed without user interaction.
  
  
  Job Scheduling Best Practices: Ensure that jobs are scheduled during off-peak hours to minimize impact on system performance, and regularly monitor job execution to handle any issues promptly.
  
  
  If you encounter any issues with the job after it has been scheduled, you may need to investigate further based on the specific job type and the context in which it is running.