Dunning Level Repeated in Dunning Run

[gajit_kumar]

Hi,

We need your help in resolving a peculiar issue we are facing relating to Dunning:

The Dunning Activity is picking up Contract Accounts repeatedly at the same Dunning Level.

For example,

the Contract Account CA - 1 contains two open items:

Document Number	Due Date	Dunning Procedure
Document 1	01.06.2014	ZA
Document 2	05.06.2014	ZA

the Dunning Procedure ZA contains 4 Dunning Levels as follows:

Dunning Procedure	Dunning Level	Days in Arrear
ZA	1	10
ZA	2	20
ZA	3	30
ZA	4	40

While analyzing the issue we are facing, we have observed that one of the scenarios when the Contract Account is repeatedly picked at the same dunning level is the following:

• if the Contract Account - CA - 1 is picked in the Dunning Activity Run at Dunning Level 3 for the Dunning Procedure ZA on 30.06.2014(when the Document 1 is reaching the days in arrear for Dunning Level 3)

• The same Contract Account - CA - 1 is picked in the Dunning Activity Run at same Dunning Level 3 for the Dunning Procedure ZA once again on 05.07.2014(when the Document 2 is reaching the days in arrear for Dunning Level 3)

The scenario mentioned above is not the only scenario when we are facing this issue of Contract Account getting picked at the same dunning level repeatedly.

The Dunning Procedure mentioned in the example has been configured as follows:

• The field - Always Dun, has not been checked.

• The correct days difference between two Dunning levels has been maintained in the field - Dunning frequency for every Dunning level.

• The field - Days in arrears, has been maintained correctly for each of the Dunning Levels

But as per the business requirement and our understanding of the behaviour of standard SAP, the Contract Account - CA - 1 which is picked at the Dunning Level 3 for the Dunning Procedure ZA on 30.06.2014, should be picked in the Dunning Activity Run only when:

the open item in the CA- 1 remains outstanding till the number of days to reach the next Dunning Level, which in this example would be reached when the outstanding item remains open for 40 days (CA - 1 would reach Dunning Level 4)

Further, As per the F1 help mentioned for the field - Dunning frequency:

The second dunning notice at dunning level 3 is prevented if you specify a dunning frequency of 10 days for dunning level 3. In that case, a dunning notice at dunning level 4 will be created ONLY on 10.07.2014, since the days in arrears for dunning level 4 have been reached.

So currently, the system is behaving in a way which is contradicting the details mentioned in F1 help.

Please advise how can we ensure that the CA - 1 is not picked up at the same Dunning Level repeatedly and confirms with the details mentioned in the F1 help.

Thanks and regards,

G. Ajit Kumar

[gajit_kumar]

Hi Anil,

Thanks for your suggestion.

Its not that the Contract Account is not getting picked in the Dunning Run.

The issue is that a Contract Account is getting picked multiple times at the same Dunning Level.

Thanks and regards,

Ajit

[AmlanBanerjee]

Hi Ajit,

Check the parameter value for the last dunning level against the dunning procedure ZA in the SPRO config.

I think it is currently configured as 2-Dun after end of dunning frequency for all line items.

Ideally it should be 3-Dunning for new overdue items only

You can find this in the following config-

SPRO-->Financial Accounting--->Contract Accounts Receivable and Payable-->Business Transactions-->Dunning--->Configure Dunning Procedure

Select the Dunning Procedure and click on display and you will find it under the parameters section.

Hope it helps...

Thanks,

Amlan

[gajit_kumar]

Hi Amlan,

Thanks for your advise.

For all the Dunning Procedures configured, the value maintained in the field - Last dunning level is "0 - No dunning, no output in log" for all the Dunning Procedures.

Moreover, the issue of Contract Account getting picked multiple times at the same Dunning Level, is happening in Contract Accounts which have not reached the last Dunning Level.

Thanks and regards,

Ajit

[Former Member]

Hi Ajit,

Have you used the dunning frequency field? I believe you issue can be resolved by using this field with days in arrears.

Regards,

Gaurav

[gajit_kumar]

This message was moderated.