The task processor job checks whether tasks are scheduled. If it finds tasks that are scheduled, but not executed, it will process them.
You can define the frequency with which the task processor will run. You can also deactivate the task processor. If the task processor job is inactive, no tasks will be processed.
1. Choose Goto → Settings → Task Processor.
A dialog box is displayed showing the current settings for the task processor.
The status of the task processor job is displayed. You can change the job's start time, the frequency for a recurring job, and the host that it will be processed on.
2. To change the settings, choose Display <-> Change.
The task processor settings are described below.
3. To save your changes, choose Continue.
The task processor job can be ACTIVE or NOT ACTIVE.
To deactivate the task processor job:
1. Choose Deactivate.
2. Confirm your entries.
The task processor job will be deactivated and the time and your user name will be recorded in the ‘Settings last changed’ field.
If the task processor job is inactive, no tasks will be processed.
To activate the task processor job again:
1. Choose Display <-> Change.
2. Specify the job frequency.
3. Select Activate.
4. Confirm your entries.
The job will be activated. The time and your user name will be recorded in the Settings last changed field.
These options set the execution time for the task processor job, and define the frequency with which the task processor job will be repeated.
You can change the execution frequency of the task processor job while it is still running. The actual time at which the task processor job runs will be determined by the system.
Run this job hourly.
The system records the time that the task processor job and the task processor job settings were last changed. The user who made the last changes is also recorded.
The target host is the host on which a background job will run. The name is specified in the profile of the SAP system. If background work processes are available on several servers, you can select the server on which a background processing request will be processed.
You can usually leave the Target host field empty. The SAP system will select the server with the lowest background workload at the time the request is started.
You should specify a server if, for example, not all servers have the same access authorizations for other systems. For example, if you need access to SAPNet R/3 frontend to process your request, select a server that provides this access.
To select a specific server:
1. Display an overview of the background servers by choosing Input Help (F4).
A background server is a server running an SAP instance that can process background jobs.
2. Specify the name of the server.
Your request will be processed on the service you specified.
Perform a ping to the RFC destination of the target server, and check whether the background work process is running. In the dialog box, double-click the destination to perform a ping and display the results.
Background jobs are assigned to classes according to priority and job category.
Class C is the default class.
You can specify one of the following classes for a job:
A Jobs with high priority that must be executed for processing to continue.
Class A jobs are always processed before jobs of other classes.
B Jobs that should be run at regular intervals
For example, jobs that send performance statistics. Class B jobs are processed before class C jobs.
C Jobs that neither fit into class A nor class B.
To be able to assign a job to class A or B, you must have authorization for ‘Background processing: background administrator’.
Settings last changed / Job last changed
These fields record when the settings and the job were last changed, and by which user.
Sets all the settings for the task to the default values proposed by SAP. The first job with the new settings will be scheduled a few minutes into the future.
Lets you display the jobs that were processed and scheduled in a specific time frame.