If you want to schedule follow-on activities for postings for postdated checks, you can recognize these because they have a new value in the Origin field of the posted document:

Customer-Specific Enhancements in Events

It is possible to add customer-specific fields to the table of checks using event 440. This could be particularly useful to add fields from the check lot to check management. These additional fields are displayed on a separate Customer Fields tab, which you can display in the check display using event 441. For more information, see the documentation of the sample function modules FKK_SAMPLE_0440 and FKK_SAMPLE_0441. They both contain commented sample code.

You can also change customer-specific fields in the check in transaction FPPDC2. The system assigns versions to the changes. You can also display the changes using event 0441, in the display transaction.

In event 0442, you can define customer-specific checks after the selection of checks, and after the entry of the posting data for the check deposit and after the transfer of checks. In this way you can prevent undesired check deposits or transfers.

In event 0443, you can define customer-specific follow-on actions after all database changes in conjunction with postdated checks (entry, change, deposit, cashing, transfer, reversal processes). You can, for example, update trigger records in your own tables, in order to prepare the follow-on actions. For more information about these events, see the documentation for the sample function modules FKK_SAMPLE_0442 and FKK_SAMPLE_0443.

The sample function modules for the following events contain enhancements for processing postdated checks:

If you have implemented your own modules in these events, check if and to what extent the changes to the sample modules can or should be used in your modules. You can find the changes by searching for “PDC” in the code.