Functions for Scheduling Program
Runs 
You want to schedule a mass run.
...
Assign a date ID and run ID that you can use later to identify the program run. all data you enter in the following steps is stored under the date ID and identification.
Danach stehen Ihnen für die Einplanung und Überwachung des Programmlaufs folgende Parameter zur Verfügung:
|
Tab page |
Functions |
What needs to be done? |
|
General Selections |
Function for entering, changing, or displaying the
parameters of a program run. |
Enter the parameters that you want to use to restrict, for example, 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. |
|
Free Selections |
Enter additional activity-specific parameters, such as additional selection parameters. |
Enter parameters as required. |
|
Technical Settings |
If required the programs are run in parallel. To execute several jobs at the same time (to synchronize them), enter the target host and the number of jobs required. 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. The split is controlled by variants in which you can specify the number and size of the intervals, and which key area each interval covers. The block size controls how many selected items are retained, for example, in the main memory. 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. For parallel runs, you can also use automatic load distribution. This means that you specify a number of jobs that the system automatically optimizes to the application servers available. |
Enter
the number of intervals and a target host. The system proposes the block size.
|
|
Logs |
The job log records status information and any errors that occur during the program run. You can make the following additional settings for the application log: · Via a specification in the field Problem Class, you determine 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) · 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 where the expiry date has been reached from the database. · The Delete before Expiry Date indicator prevents the log from being deleted before the expiry date specified. |
Choose the log you require. |
Additional functions
|
Function |
Meaning |
What needs to be done? |
|
Display/Change |
Information or completion of parameters |
Choose whether you want to display or change the program run. |
|
Copy |
Copy the parameters of a program run |
Specify a name for the program run that you created using the copy function. |
|
Adjust |
Move
the run parameters of a program run by n days. |
|
|
Schedule |
Defines when the run is to be started |
Enter the start date and time, or set the Start Immediately indicator. |
|
End Early |
Terminates a run |
|
|
Restart Run |
Restarts runs that have been stopped. |
|
|
Delete |
Deletion of a program run |
|
|
Deactivate Old Runs |
You can use this function to exclude runs that are no longer required from the display of the input help. To remove the data from the database permanently, in the menu of the mass activity, choose Program Run ® Delete, or in the SAP menu, Periodic Processing ® Administration of Mass Processing ® Delete Parameter Records. |
|
|
Environment |
Depending on the application area, enables you to navigate to other transactions. |
|
|
Special Features for Creating Correspondence |
||
|
Date and periods |
Defines which correspondence is created. The system
only creates correspondence for a selected period (for example, correspondence
to be created each week or all account statements for July). The
correspondence variants are compared in the contract account master record.
|
Specify the frequency required. |
|
Number of spool requests |
In the correspondence print run, you can summarize the spool requests at job level and thereby drastically reduce the number of spool requests. |
In
the Implementation Guide for Contract Accounts Receivable and Payable,
set the indicator Spool Aggregation at Job Level Required, under
Technical Settings
® Activate Performance Improvement
for Mass Runs.
|
Handling Parameter
Records
If you do not require all of the old parameter records from the mass runs you
have carried out, you can:
· Hide parameter records (SAP menu: Periodic Processing ® Administration of Mass Processing ® Hide Parameter Records), in particular, to display only the runs that are important for you in the input help.
Physically remove old parameter records from the database (SAP menu: Periodic Processing ® Administration ® Delete Parameter Records).
See also the sections
Creating Counters for
Mass Runs and
Enhanced Message
Management.