Show TOC

Function documentationFunctions for Scheduling Program Runs


You want to schedule a mass run.


The functions listed below are available on the individual tabs:




General Selections

Function for entering, changing, or displaying the parameters of a program run. You can only make changes to program runs that have not been scheduled yet.

Enter the parameters that you want to use to restrict the items to be processed (for example, company code, contract account, business partner). Enter no selection criteria if you want the program run to process the whole data set.

Tab(s) for activity-specific selections, for example, Custom Selections

Enter additional activity-specific parameters, such as additional selection parameters.

Enter parameters as required.

Technical Settings

If you wish, the programs are run in parallel. To run several jobs simultaneously (run in parallel), you enter the target servers or server groups and the number of processes. Several jobs are then started simultaneously in one program run, each processing one of the intervals in parallel. You can divide the intervals according to different criteria. This division is controlled by variants in which you can specify the number and size of the intervals, and which key area each interval covers. If you want to run the program in parallel, either specify a target host and the number of jobs assigned, or specify several target hosts with the number of jobs assigned to each one. Or instead, for running the program in parallel, you specify a server group and the number of jobs assigned, or specify several server groups with the number of jobs assigned to each one. For parallel runs, you can also use automatic load distribution. This means that you specify a number of jobs that the system automatically distributes to the application servers available.

The block size is used differently by the individual mass activities. For example, you can control how many selected items are held in the main memory or how large a COMMIT block is. For information about using the block size, see the documentation for the individual mass activities.

  1. Select either Automatic Load Balancing or Explicit Load Balancing or Explicit Load Balancing with Server Groups and enter the number of jobs and target hosts or server groups.

  2. Select a variant. The system proposes the block size.

    If the program run is to be executed by a single job (that is, not in parallel), you do not have to make any technical settings.


The job log records status information and any errors that occur during the program run. The application log contains business-relevant information. You can make the following additional settings for the application log:

  • By making a specification in the Problem Class field, you specify the importance that a message must have to be output in the application log. For production, SAP recommends class 2, for testing, class 4:

    • Very important (1)

    • Important (2)

    • Average (3)

    • Additional information (4)

    If you specify class 3, logs with lower classes are also output, that is, also 1 and 2.

  • The expiry date specifies the earliest date on which the log expires. It can also influence the event in which the log is deleted. This is particularly relevant because from the application log, you can schedule jobs, and delete logs from the database where the expiry date has been reached.

  • The Hold until Expiry Date indicator prevents the log from being deleted before the expiry date specified.

  • The application logs are displayed in Enhanced Message Management (transaction EMMA). There you can create and monitor clarification cases for error messages.

Choose the log you want.

Further Functions





Switch between display and change mode.

Choose whether you want to display or change the program run.


Copy the parameters of a program run

Specify a name for the program run that you created using the copy function.


Copy the run parameters of a program run and move the run date and other date fields by n days. This function is not supported in all applications.


On the Technical Settings tab, you can create variants dependent on the parallelization object for the split into intervals. If dynamic interval creation is not supported for a mass activity, you can change the variants manually. If the underlying data changes frequently, you should regenerate the variants regularly to achieve an even interval distribution.

To create a variant:

  1. Choose the button Variant Maintenance (Variant Maintenance).

  2. Choose New. You can specify either the interval size or the number of intervals.

  3. Choose Execute.

    To display the intervals created or to edit the variant, double-click on a variant name on the initial screen of variant maintenance.

Simulation Run

In most mass activities, you can repeat a run as a simulation run as many times as required; however, you can only execute it as an update run once. After you have executed a simulation run, the parameters remain ready for input. When you schedule a run that has already been executed as a simulation run, three actions are carried out:

  1. Deletion of temporary interval distributions

  2. Deletion of jobs

  3. Deletion of the application log

Set the Simulation Run indicator and schedule the run.


Defines when the run is to be started

Choose the Schedule Schedule Program Run (Schedule) pushbutton. In the dialog box that appears, you can choose between an immediate start in the background, a start in the background with specification of start date and time, or a start in the background via a job container of the job commander.

End Early

Terminates a run. This means that if the program is running, once the current interval has been processed, all jobs are terminated from this command.

Restart Run

Restarts runs that have been stopped.


Deletion of a program run. All parameters of the program run are deleted. If the program run has already been scheduled or started, it cannot be deleted.

Deactivate Old Runs

This excludes runs that are no longer needed from being displayed in the entry help. To remove the data from the database permanently, in the menu of the mass activity, choose Start of the navigation path Program Run Next navigation step Delete End of the navigation path. Or on the SAP Easy Access screen, choose Start of the navigation path Periodic Processing Next navigation step Administration of Mass Processing Next navigation step Delete Parameter Records End of the navigation path.


Enables navigation to other transactions dependent on the application area. (Not available in all mass activities.)