Reversal of dunning run in SAP

1 Introduction
This document discusses how a dunning run can be reversed. Reversal of
dunning run means changes are required both at the customer master level
and at the document level since dunning updates the customer master data
and the open items for the customers that have become overdue
At the customer master level the last dunning run date and dunning level is
required to be changed to the immediate prior run for that customer.
At the document line item level the fields dunning date and dunning level are
required to be restored to those corresponding to the immediate prior run.

2 Background
In a typical business scenario it might be possible that a dunning run was
executed by mistake though it was not supposed to be executed.
The issue of dunning letters cannot be undone. However changes can be
made in the customer master data and transaction data. This change in
master and transaction data is described below in the document.
3 Procedure and Aspects
involved

SAP provides a standard program to undo the dunning run which has already
been run. The program is RFCORR14. This program can be executed in the
test run and once the results of the test run are fine, the same can be
executed in the real run. Running the program in the real run requires that
code changes are made to the program to hard code name of the user who
can run the program. This is done to ensure that only users who have access
can run the program. Unauthorized users are prevented from running the
program.
An instance of reversal of dunning run:
Selecting a particular customer 172200269 for dunning
Customer Master Data before the execution of dunning run:

Documents that are overdue for that customer:

Carrying out a dunning run for the selected customer:

Subsequent to the dunning run the customer master data changes as below:

The line items in the customer master data also get updated as under with the new dunning
date and the new dunning level.
Customer line item display:

At the document level, the last dunned date and last dunning level gets updated as shown
under:

Now we reverse the dunning run which was executed above:
Using the program RFCORR14 to reverse the dunning run

Carrying out a test run giving the run date and identification:

In the test run we can see that changes are made both at the document level and at the
customer master level:

If the results of the test run are successful, we carry out the real run by checking the field
Update run with update to BSEG:

In case the name of the user is not hard coded in the program we get the following error:

Once updated the error does not appear.
The customer master data and the document data changes as shown below:

In the customer master, the dunning date changes to the previous date. The dunning date
changes from 12.09.2012 to 31.05.2012 as shown below:

At the document level also, the last dunned date changes to previous dunned date
immediately prior to execution of the dunning run. The dunning run will appear as blank and
the dunning level becomes 0 in case the dunning run which was reversed was the first run
for that particular line item:

Thus we see that the program RFCORR14 can be used for reversal of dunning run that was
incorrectly dunned.
In order to prevent unauthorized use SAP has placed a check that the user who is authorized to
run the program be hard-coded in the program. This prevents unauthorized users from reversing
the dunning run.