You have configured the system to allow dunning using collection agencies (refer to Configuring Dunning Using Collection Agencies).

1. You send the collection agency all the open dunning items that have reached the final dunning level.

The system assigns all these items a dunning block indicator to prevent any further dunning notices from being issued in the meantime. It saves them in a file named DUNN_<CLIENT>_<RUN DATE>_<RUN NUMBER>

There is a separate include program that defines the logical path that the file is saved under. You can change the path if necessary. The include also contains the definition of the dunning block indicator.

2. The collection agency sends you a number of files containing data about the interest and charges incurred.

For each company code there is a separate file, which is in the same format as the file that you sent to the collection agency. In order for the R/3 System to be able to read these files, they must be named DUNN_<CLIENT>_<COMPANY CODE>_<STATEMENT NUMBER>

3. Using the electronic statement functions, the R/3 System reads the files, checks that the data is consistent with previous statements, and converts it to MultiCash format. It then reads the statement file and the line item file and posts the interest and dunning charges.

In the posting documents, the R/3 System enters the collection agency’s reference number in the BSEG-XREF1 field.



The electronic account statement functions do not support the use of one-time accounts.

4. You create a file of all the items that have been cleared within a given period, which you send to the collection agency. You create the file using the RFIDSE_DUNN_INF program. The file is named DUNN_<CLIENT>_<RUN DATE>_<COMPANY CODE>