How To Fix SCWN137 - Job & started; check the progress in transaction SM37

SAP Error Message - Details

• Message type: E = Error

• Message class: SCWN - Messages Note installation and management

• Message number: 137

• Message text: Job & started; check the progress in transaction SM37

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 SCWN137 - Job & started; check the progress in transaction SM37 ?

  The SAP error message SCWN137 indicates that a job has been started, and you should check its progress in transaction SM37. This message typically arises in the context of background jobs in SAP, particularly when a job is scheduled to run but has not yet completed or is experiencing issues.
  Cause:
  
  Job Scheduling: The job has been successfully scheduled and started, but it may still be running or waiting for resources.
  Long Processing Time: The job may be taking longer than expected due to the volume of data being processed or system performance issues.
  Job Failure: The job may have encountered an error during execution, which could prevent it from completing successfully.
  Resource Contention: Other jobs or processes may be consuming system resources, causing delays in job execution.
  Configuration Issues: There may be issues with the job configuration or the environment in which it is running.
  
  Solution:
  
  
  Check Job Status:
  
  Go to transaction SM37 (Job Monitoring).
  Enter the relevant selection criteria (e.g., job name, user, date range) and execute the report.
  Look for the job in question and check its status (e.g., Running, Finished, Canceled, or Error).
  
  
  
  Analyze Job Logs:
  
  If the job has finished, check the job log for any error messages or warnings that can provide insight into what went wrong.
  If the job is still running, you can monitor its progress and see if it is making progress or if it is stuck.
  
  
  
  Review System Performance:
  
  Check system performance metrics to see if there are any bottlenecks (CPU, memory, I/O).
  Use transaction ST22 to check for dumps that may have occurred during job execution.
  
  
  
  Adjust Job Parameters:
  
  If the job is taking too long, consider adjusting its parameters or breaking it into smaller jobs if possible.
  
  
  
  Re-run the Job:
  
  If the job has failed, you may need to correct any issues identified in the logs and re-run the job.
  
  
  
  Consult Documentation:
  
  Review any relevant SAP documentation or notes related to the specific job or process you are running.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM36: Job Scheduling
  ST22: Dump Analysis
  SM21: System Log
  ST03N: Workload Analysis
  
  
  
  SAP Notes: Check the SAP Support Portal for any notes related to the specific job or error message for additional troubleshooting steps or known issues.
  
  
  Performance Tuning: If jobs frequently take too long, consider reviewing system performance and tuning the environment for better efficiency.
  
  
  By following these steps, you should be able to diagnose and resolve the issue related to the SCWN137 error message in SAP.