Here,
correspondence that occurs regularly (such as invoices) or correspondence
requested individually (such as account statements) is created.
In contrast to event-controlled correspondence creation, here it is not the
application program (for example, dunning program) that creates the
correspondence data; instead, the correspondence creation run determines the
data and stores it in the correspondence
container for
printing.
To check the data, start the correspondence creation run in simulation mode. For the update run, after the check, start the creation run without the simulation indicator.
Using the selection criteria, you can define, for a correspondence creation run, which correspondence is to be considered. For example, in a program run you can include all invoices for business partners A-M that are due in calendar week 31.
The desired correspondence variant must be defined in the master record of the contract account to be processed.
...
1. Enter the parameters for the correspondence creation run (see Functions for Scheduling Program Runs).
2. Schedule a correspondence creation run or start it immediately (see Functions for Scheduling Program Runs).
3. Using the correspondence variants defined in the contract account master record, the correspondence run determines the relevant correspondence data and stores it in the correspondence container (one data record per print output).
The correspondence data determined is in the correspondence container.
To print the correspondence you can now perform the correspondence print run (see Printing Correspondence).