How To Fix PYC_CONT012 - Job is working now; job status is &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: PYC_CONT -

• Message number: 012

• Message text: Job is working now; job status is &1 &2

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 PYC_CONT012 - Job is working now; job status is &1 &2 ?

  The SAP error message PYC_CONT012 indicates that a job is currently running, and its status is displayed as &1 &2, where &1 and &2 are placeholders for the actual job status and additional information. This message typically arises in the context of SAP's Controlling (CO) module, particularly when dealing with processes that require job scheduling.
  Cause:
  
  
  Job is Running: The primary cause of this error is that a background job related to the process you are trying to execute is already in progress. This can happen if:
  
  A previous execution of the same job has not yet completed.
  There are overlapping job schedules that conflict with each other.
  
  
  
  Job Status: The job status indicated by &1 &2 can provide more context. For example, if the status is "active," it means the job is currently executing. If it is "scheduled," it means it is queued to run but has not started yet.
  
  
  Solution:
  
  
  Wait for Completion: If the job is currently running, the simplest solution is to wait for it to complete. You can monitor the job status in the SAP job management transaction (e.g., SM37).
  
  
  Check Job Logs: Review the job logs to understand why the job is taking longer than expected. This can help identify any issues that may need to be addressed.
  
  
  Cancel or Delete Job: If you determine that the job is stuck or needs to be restarted, you can cancel or delete it using transaction SM37. Be cautious with this approach, as it may affect data integrity or processing.
  
  
  Adjust Scheduling: If overlapping jobs are a recurring issue, consider adjusting the scheduling of jobs to prevent conflicts. This can be done in the job scheduling settings.
  
  
  Consult Documentation: Refer to SAP documentation or support for specific guidance related to the job in question, especially if it is a standard SAP job.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM37: Monitor background jobs.
  SM36: Schedule background jobs.
  SM21: Check system logs for errors.
  
  
  
  Job Monitoring: Regularly monitor job statuses to prevent overlaps and ensure timely completion of processes.
  
  
  Performance Tuning: If jobs frequently take too long to complete, consider performance tuning of the underlying processes or database.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to job scheduling and execution.
  
  
  If the problem persists or if you encounter additional errors, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.