Description
RFDKLI20 recreates SD and FI credit data after organizational changes.It can also be started via transaction F.28.
You have to run this report after the following changes:

General changes that affect SD and FI:

• Settings that change the determination of the credit control area:
Assignment from company code, entry in customer master data, entry insales area data, user exit.

• Currency of credit control area.


• Assignment of customers to credit accounts.


• Risk class in master data of credit account (transaction FD32). Caution:
If nothing was changed except for the risk class, you can use RFDKLI20but it is excessive in this case. If only the risk class was changed itis sufficient to run RVKRED09.

FI-specific changes:


• Classification of a difference reason as a disputed item or non-disputed
item was changed.

• Change to property #Without Credit Management# of a reconciliation
account with exception handling.

• Change to property "Credit-Limit Relevant" of a special general ledger
indicator.

After one of the changes described above, you have to start this reportbecause


• In clearing, exactly the amount in credit limit currency is reset and
the amount must be available translated into the correct currency.

• The control area was determined from the company code in a posting and,
in the case of a change to this assignment, the earlier postings must beassigned to this new control area so that the total of receivables isdisplayed correctly.

Features

FI part:
The report reads the open items of all selected customers and determinesthe amount of the item in the (new) currency of the current correctcontrol area and enters this amount in the document.
This recreates the control area-specific credit data.

SD part:
The report updates credit data (credit control area, credit account,credit currency, credit value, risk class) in sales documents within aninternal VA02. This means that the document is read, the credit data ischanged, and then saved.
This can, under certain circumstances, cause further changes in thedocument changes that would also take place on a manual execution ofVA02 and new save.
The info structures S066 and S067 affected are not deleted (as forRVKRED77); instead, with the internal VA02, the SD credit values for theold settings are written off from the info structures and then postedagain for the new settings.

The following general statements are valid:
Since, under certain circumstances, database changes with high runtimeshave to be carried out, the report should be started in a batch run andnot called in dialog. The report should also be run in a period whenpostings are not being performed (as far as possible).

Selection
You can also start the report for an individual customer in a controlarea.