Ansicht
Dokumentation

Changes to Dunning of Customers/Vendors ( RELNFI_46A_DUNNING )

PERFORM Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Short text

Changes to Dunning of Customers/Vendors

Scope of Functions

New Business Transaction Event:

A Business Transaction Event has been added: P/S Event 1719. This event comes before the printing of the dunning notice (Event 1720). The sample function module SAMPLE_INTERFACE_00001719 describes the interface.

If you wish to run your own function modules at this event, enter your function modules in Customizing in the activity "Use Business Transaction Events" for the Publish & Subscribe Event 1719. If you do not wish to use the event, you do not need to do anything.

First dunning notice in a new dunning area

If documents exist for dunning and have a dunning area that has not yet been entered in the customer master record, the system uses the specifications such as the dunning procedure and the date of the last dunning notice from the standard dunning area (dunning area "blank").

A new development is that a "0" is entered as the date of the last dunning notice in this case, because a check should not be run on the dunning interval (dunning frequency) for the first dunning notice in the new dunning area. We work on the assumption that a document with a new dunning area will not have been dunned during the last dunning run in the standard dunning area.

Periodic, repeated scheduling of the dunning selection

You can use a variant to schedule report program RF150SMS as a job with a repeat period. The program functions as follows: The dunning run defined as a variant in the program is used as a template for the dunning run to be scheduled. The date parameters of the dunning run to be scheduled are adjusted here. The identification of the new dunning run is taken from the ID of the template and the date on which the program is run. (See also the documentation on report program RF150SMS).

Here is an example of how program RF150SMS determines the ID and parameters of the dunning run to be scheduled.

Dunning run as a template (parameters in report RF150SMS): Date 2.3.1999, identification M1. Customer D, company code 0001. Dunning date: 2.3.1999, documents posted up to: 2.1.1999.

The program is run on 2.15.1999. The scheduled dunning run is: Date 2.15.1999, identification M1, customer D, company code 0001. Dunning date 2.14.1999, documents posted up to 2.14.1999.

The date details for the dunning run are taken from the date of the identification and differences in the date parameters of the template compared with the identification date.

Dunning in the Schedule Manager

Report program RF150SMS is also used as a basis for scheduling a dunning run in the Schedule Manager. You can call up the dunning selection log from the Schedule Manager monitor. After the dunning selection has taken place, you can go from the Schedule Manager to the screens for changing the dunning notice or for scheduling the printing of the dunning notices. The printing of the dunning notices cannot be scheduled from the Schedule Manager.

For more information about the Schedule Manager, see the SAP Library under CO - Schedule Manager.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

In Customizing, you must specify at which events the additional components are to be called up. Product information and, where necessary, a partner ID must be defined in the system, and a user-developed function module must be assigned to one or more of these events. When a product is activated at client level, the additional components can be called up. You can make all the necessary settings in the activity Use Business Transaction Events

Effect on batch input

Changes to the Interface

When entering parameters for a dunning run under Free selections, you can now enter the field names directly or via possible entries.

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4734 Date: 20240603 Time: 130828     sap01-206 ( 95 ms )