Ansicht
Dokumentation
RFFMKWD0 - Supplement for Assignment Dunning Procedure for Dunning Area
Addresses (Business Address Services) PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Title
Supplement of Assignment Dunning Procedure to Dunning Area
Purpose
This program writes the dunning procedure and corresponding dunning areas in the selected customer and vendor master data.
Always when no entry for the combination company code/dunning area/ dunning procedure exists in the customer/vendor master record, this program creates a corresponding data record. The program dunning procedure and areas are taken from the entries that you maintained in the Customizing of Funds Management Government.
Integration
Prerequisites
A dunning procedure must be defined for dunning area empty.
The current valid assignment of dunning procedure to dunning area that the program should enter in the selected dataset must be maintained in the Customizing of component Funds Management Government in step Assign Dunning Procedure to Dunning Area.
Features
Selection
On the selection screen you must select whether you want to process customers and/or vendors. In order to limit the selection more, you can specify the subledger accounts that the program should process: either you specify the subledger account number (n) in the SAP system or subledger account numbers(n) as a preprocedure. If you specify the subledger accounts from preprocedure, the program selects only these specifications.
You can also specify whether the program should copy the following fields from the dunning area empty to the customers/vendor master record for the new assignment of dunning procedure to dunning area.
- Dunning block
- Dunning recipient
- Processor
Standard Variants
Output
The program generates a list with the following:
- Number of entries to be created in the customer master records
- Number of entries created in customer master records
- Number of entries to be created in the vendor master records
- Number of entries created in vendor master records
Differences between the number of entries to be created and entries already created can be caused by some accounts being blocked by another user.
Activities
Example
ABAP Short Reference General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 2692 Date: 20240520 Time: 115608 sap01-206 ( 49 ms )
