How To Fix WZ060 - Job &1 &2 cannot be started immediately

SAP Error Message - Details

• Message type: E = Error

• Message class: WZ - Workflow: Model objects

• Message number: 060

• Message text: Job &1 &2 cannot be started immediately

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 WZ060 - Job &1 &2 cannot be started immediately ?

  SAP Error Message:
  
  WZ060: Job &1 &2 cannot be started immediately
  
  Cause:
  This warning message occurs when you try to start a background job immediately, but the job cannot be started right away. The reasons can include:
  
  The job is scheduled to start at a later time (not immediately).
  The job is already running or is in a queue waiting for resources.
  The system or the background processing server is busy or not available to start the job immediately.
  The job’s start conditions or dependencies are not yet met.
  
  
  Explanation:
  In SAP, background jobs can be scheduled to run immediately or at a specified time. If you attempt to start a job immediately but the system cannot do so (due to scheduling, resource availability, or other constraints), this warning is issued.
  
  Solution:
  
  
  Check Job Scheduling:
  
  Go to transaction SM37 (Job Monitoring).
  Find the job by name or user.
  Check the scheduled start time and status.
  If the job is scheduled for a future time, either wait for that time or reschedule the job to start immediately.
  
  
  
  Check Job Status:
  
  Verify if the job is already running or stuck.
  If stuck, consider canceling or deleting the job and rescheduling it.
  
  
  
  Check Background Processing Servers:
  
  Use transaction SM51 to check the active application servers.
  Use transaction SM66 to check active processes.
  Use transaction SM37 to check if the background work processes are free.
  If all background work processes are busy, the job cannot start immediately.
  
  
  
  Reschedule the Job:
  
  If immediate start is required, delete the existing job and create a new job with immediate start.
  Alternatively, use transaction SM36 to schedule the job with the desired start time.
  
  
  
  Check System Load and Resources:
  
  High system load or insufficient background work processes can delay job start.
  Consider increasing the number of background work processes if this is a frequent issue (parameter rdisp/wp_no_btc).
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM36 – Define background job
  SM37 – Monitor background jobs
  SM51 – List active application servers
  SM66 – Global work process overview
  
  
  
  SAP Notes:
  
  Check SAP Notes related to background job scheduling and processing if the problem persists.
  
  
  
  Background Job Concepts:
  
  Background jobs are processed by background work processes.
  Jobs can be scheduled with immediate or delayed start.
  Jobs can have dependencies or start conditions.
  
  
  
  
  Summary:
  The warning WZ060 indicates that the job you want to start immediately cannot be started right now due to scheduling or resource constraints. Verify the job’s schedule, status, and system resources, and adjust the job scheduling or system configuration accordingly.