Show TOC

 Execution of Standing Orders

Procedure

  1. Choose Start of the navigation path Periodic Tasks Next navigation step Standing Order Next navigation step Parallel Processing. End of the navigation path

  2. Specify the bank area for which the standing orders are to be executed.

  3. Enter a number of standing orders for each package.

    The system creates the packages with this size so that the standing orders from accounts that are linked by one or more standing orders are always processed in the same package. The package size depends on the data constellations and system configuration, and needs to be tested.

    Note Note

    Note on the technical specifications of the Parallel Processing function:

    You can activate the complete log by setting the indicator Complete Log. You should only do this, however, in exceptional circumstances. This is because approximately 100 entries are written in the application log for each standing order, which can take up a large amount of memory space. For performance reasons, only make use of this feature if you are looking for errors.

    You can set the No Connection to External Payment Transaction System indicator to prevent the transfer of payment orders with external recipients to the external payment transaction system during the standing order run. These payment orders can then be transferred outside of end-of-day processing by using the RFBKPOEX report. This enables high performance in end-of-day processing.

    End of the note.

Result

The system creates the appropriate payment orders (with the current posting date of payment transactions as posting date) and, in the case of external recipients, transfers them to the payment transaction system. The system then increases the next run date for the processed standing orders in the account master record.

The system executes only the active versions of standing orders.