If the background job in SAP is in released state, it will run at the mentioned time or when respective event occurs (as per the job definition). If for any reason, you would like to hold the job(s) from execution, you can do the same using SM37 transaction.
In real time scenarios, you may need to hold few jobs from execution like
- After system refresh, you may have to hold jobs from execution in target system because the target system consists of source system jobs and they shouldn’t run. So, it is suggested to hold all the jobs from execution and release only required jobs and basis standard jobs(housekeeping jobs)
- Sometimes, there might be duplicate schedule of same job and you want to hold the duplicate job to prevent multiple executions
In these cases, to hold the jobs to prevent from execution, we need to set the status of those jobs from “Released” to “Scheduled”. To do the same, we have login to SAP system and go to transaction SM37 which will result in below screen.
In the above screen, select the job status as “Released” and keep all other options as shown above and execute. This will list down all the released status jobs.
From the list, select tick those jobs that you would like to prevent from execution and change the status from “Released to Scheduled” as shown below:
Then all the selected jobs status will be set as “Scheduled” and those jobs won’t get executed till you release them again.
