In the following section there is a description of how you organize end of day processing with the aid of event control. The corresponding reports are included as jobs by means of transaction "job definition" and can, therefore, run automatically.

To control these jobs, events are defined for every function that inform the job administration when the function has run successfully. This means that the next step is only started when the final event of the previous function has been reached. The event that has run previously must be stored in the subsequent jobs. This is done with the attribute "Start after event XY". If this is a cross-bank area step, the step is triggered more than once. The parameter is the bank area.

You find an overview of the reports and the corresponding events in the following table. (The standing order line only applies to banks):

The final event of a function within a chain is triggered when

• all accounts have been edited and
• no termination occurred.

For some accounts, errors could have occurred during editing, for example, because they were not active. These accounts are then blocked for all further steps of the run. However, the event is triggered so that all the other accounts can be further processed in the next steps.

In this case, for control purposes, proceed as follows:

The event is not triggered if a mass run was terminated (for example, due to a system error). If this is the case, the accounts of the subsequent runs are not edited and the batch processing is interrupted. The corresponding runs must also be started with "Restart". or "Restart individual step".