You want to schedule a mass run.
The functions listed below are available on the individual tabs:
Tab | Functions | Action |
| 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, | Enter additional activity-specific parameters, such as additional selection parameters. | Enter parameters as required. |
| 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. |
|
| 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:
| Choose the log you want. |
Further Functions
Function | Meaning | Action |
| 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 | To create a variant:
|
| 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:
| Set the |
| Defines when the run is to be started | Choose the |
| 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. | |
| 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. | |
| 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 . Or on the SAP Easy Access screen, choose . | |
| Enables navigation to other transactions dependent on the application area. (Not available in all mass activities.) |