Each application server within an SAP System has a configurable number of background work processes1 designated for processing batch jobs. If too many background jobs are released directly in SAP, and if they are not controlled by an external scheduler, their traffic can result in using up work processes meant for scheduled jobs.
Unexpected jobs can only be controlled and automated when an external job scheduler is used. SAP provides APIs to retrieve a list of intercepted jobs, allowing the external scheduler to decide when the jobs will run.
The interception feature must be explicitly activated on the SAP system. When activated, the SAP CCMS compares each job that is about to run against the intercept criteria.
SAP user releases a job to run a large report that is resource intensive and takes a long time to complete.
- Set intercept criteria to match the job description.
- External scheduler polls intercepted job.
- External scheduler schedules job to run during non-work hours.
Three useful policies for SAP job interception include:
- No interception required
If there are no users in the SAP systems that can release jobs, and if no SAP applications that create their own jobs are in use, then interception serves no purpose and it does not need to be used.
- Some jobs are intercepted
By carefully filling the criteria table, you can intercept only certain categories of jobs. For example, if you find that your financial end users are causing stoppages by ad-hoc selected jobs, you could put their usernames in the criteria table. Unfortunately the criteria do not easily allow you to match all background jobs started by SAP programs unless they have a job name that starts with a specific character string.
- All jobs are intercepted
Usually the most useful policy is to intercept all jobs. When an external scheduler is used to run all batch job scheduling, the volume of jobs started outside of the external scheduler should be low. Every job started outside of the external scheduler has the potential of interfering with the start time of other jobs. To counter this, make sure every job is intercepted so that they will adhere to the preferred schedule. This is also true for background jobs started by the user DDIC.2