Dunning block in customer

10/20/23

Reply: 4

Auto translated

Hello,
I have a requirement that a dunning block is automatically set in the customer master when an invoice in the dunning run has reached the new dunning level 3. After reaching this dunning level, the customer should no longer be dunned, but the open items are transferred to an external procedure for further processing.
Does anyone know a UserExit in FIBF that can be used.
With kind regards
deab0224

You must be logged in to post a reply.

4 Answers

kerger66 10/20/23, 12:42 PM
Hello,
I think you may be able to do this via the dunning printout. SAP extension F150D001 is specified there.
Kessi
MrBojangles 10/20/23, 12:42 PM
Hello deab0224,
whether you can actually intervene in the update of the customer master from the dunning run, I honestly do not know, I think rather not.
But a design of the BTE 1060 or 1061 (process interface) brings the same effect. With BTE 1060 you could set a dunning block for all items that have 3 as the "old" dunning level, with BTE 1061 you could delete the item completely from the dunning list.
Example coding BTE 1061:
[code=generic]
IF I_MHND-MAHNS >= 3. "old dunning level >= 3?
C_DEL_DU = 'X'. "--> Delete item
* If necessary, return another info to the dunning run log here
LS_FIMSG-MSGTY = 'I'.
...
APPEND LS_FIMSG TO T_FIMSG.
ENDIF.
[/code]
Probably the design of the process could be even more clever, if for example one could start with the transfer of the OP's to the external procedure to set the field "Judicial dunning procedure" in the master record. In this case, an (internal) dunning letter is only generated if new account movements have been recorded on the customer...
Have fun with SAP...
Cheers
MrB.
Blog
Last edited on 26.03.20 13:22
kerger66 10/20/23, 12:42 PM
Hello,
During the dunning run and printing, the documents are also changed and the dunning levels are written in, so a dunning block should not be a problem.
Kessi
MrBojangles 10/20/23, 12:42 PM
kerger66:
During the dunning run and printing, the documents are also changed and the dunning levels are written in, so a dunning block should not be a problem.

Unfortunately it is, at least not without modifications. The update of the master record as well as the documents with the new dunning level is done in the function module CHANGE_DUNNING_DATA, which is called in the course of the dunning print. Unfortunately, there is no BADI or BTE call in the environment of this function module, in which the additional update of the dunning block could be built in...
Have fun with SAP...
Cheers
MrB.
Blog