Dunning for some open items is not triggering

[Former Member]

Hi Experts,

Industry:- Retail Industry, Online shopping

I have a business requirement in which a Contract account should have only one dunning level irrespective of the number of orders and their respective due dates. This is customized using event 300 and..This is the present setup of the system and is working as desired.

Please see the screenshot above,

Now I have a scenario,

for the order 201831536 dunning level 21 is reached. The dunning run has occured on 15.07.2013 and at that time, order 202051809 has n't reached its due date. Mean while customer has made the payment for the order 201831536.

But with the next dunning run, this order 202051809 has n't been dunned anymore, eventhough its due date is crossed. Do i need to check in some events?

Thanks in advance!

Lakshmi.

[william_eastman]

Lakshmi:

This would be fully due to your event customization as it would not behave like that by standard.  Please check the logic in your events.  You cuold test by removing your customization and verifying behavior afterwards.

regards,

bill.

[AmlanBanerjee · Accepted solution]

Hi Lakshmi,

As suggested by Bill, event 300 would be the probable root cause of the issue.

However,apart from the customization at event 300, there can be other possible reasons as well for the new order not being dunned.

Go to the Contract A/c config

Contract Accounts Receivable and Payable--->Business Transactions-->Dunning-->Dunning by Dunning Procedure-->Configure Dunning Procedure

Select the Dunning Procedure and click on display.

Check the value of parameter Do not reduce Dunning level.

This field has the effect that the dunning levels of the items in the dunning run are not restricted to the dunning level of the next highest dunning notice.

Check this indicator.

Hope it helps

Thanks,

Amlan

[Former Member]

Hi Amlan,

Geniuos!!

It worked like charm. I have set this indicator. This order has a dunning procedure, for which this indicator is unset.

Keep up the good work.

This solved my issue partially. I have an other scenario,

My business scenario is that One BP will have only one dunning level for a particular dunning procedure.

Business partner ABC

Order        Duedate                   dunning level

123            14.08.2013                 20

456            02.09.2013                0

789            03.10.2013                0

With next dunning run from 29.08.2013 both of the order 123, 456 will reach dunning level 25.

Order        Duedate                   dunning level                   due amount

123            14.8.2013                 25                                       4Euro

456            02.09.2013                25                                      5 Euro

789            03.10.2013                0                                       30 Euro

Next dunning run is executed on 10.09.2013, which is the last dunning level in which the dunning activity looks for due amount. If it is less than 10 Euro, it has been written off. If not handed over to collection agency.

Dunning run 10.09.2013

Order        Duedate                   dunning level                   due amount         write off

123            14.8.2013                 30                                       4Euro                 yes

456            02.09.2013                30                                      5 Euro                yes

789            03.10.2013                0                                       30 Euro

For this BP, the latest duuning level on table FKKMAKO is 30.

next duuning run on 15.10.2013, order 789 is not dunned. In this case, does SAP normally triggers dunning for this order 789? or do i need to customize it with the help of table  TFK047B?

In debugging In event 304, I have found dunning level as 0 for this new order 789. it_fkkmavs-mahns  i_fkkmavs-mahns = 0.

Any Help is  appreciated.

Lakshmi.

[AmlanBanerjee]

Hi Lakshmi,

Check the application log for the dunning proposal, as to why standard SAP is not picking the last order even after the due date has elapsed.

I think you will definitely find a way through after going through the application log (SLG1) for the proposal run.

Thanks,

Amlan

[Former Member]

Hi Amlan,

Okay. Then the std procedure will normally trigger dunning for the scenario that I have mentioned above. Then perhaps it is in customization they may be spoiled it. I will look into it.

Thanks,

Lakshmi.