Hi Dieter,
I think your requirement can be mapped in SAP with a custom enhancement in event 300.
This event enables you to post-process the dunning proposal created in the dunning proposal run
Scenario
Initially, an invoice is raised on 1st July and the say the due date of the same is 29th of July.
So on 30th July it is over due and is eligible for dunning.
Now the second invoice is raised on 1st August and you want to sent the dunning notice along with the invoice.
Assuming my above scenario is correct, I would recommend you to make an enhancement in event 300, which will remove the particular contract account from the Dunning Proposal run until it finds a invoice that has been posted with a posting date same as the dunning issue date.
The pre-requisite would be you have to execute the invoicing run first and then execute the dunning.
So, on 30th July when dunning proposal will run, it wouldn't find any invoice posted for the date and would remove the account from dunning and it will continue to happen for 31st July as well.
Now on 1st August, when the dunning proposal will run, it would find an invoice which has been posted for the particular issue date and will go ahead with the dunning run to generate a notice which then can be collated with the invoice to be sent to the customer.
The drawback of this would be that the incremental change in the dunning level would solely depend on the invoicing run executed in the system rather than from the configuration.
Hope it helps...
Thanks,
Amlan
