cancel
Showing results for 
Search instead for 
Did you mean: 

Dunning blocked by previous dunning run

Former Member
0 Kudos

Dear all,

I have tried to troubleshoot so many times and I have to come here for help..

I have captured pictures to provide necessary info as much as possible..

Situation:

There's an overdue invoice for customer 100001, but no dunning notices generated as "Account was blocked by dunning run <date>". Note it is <date> only, without <identification> provided in the Dunning Log.

Intention:

To test dunning run at level 1, 2 and 3.

I'm not sure if I missed any step. Can you give me potential cause?

Thank you.

There is an overdue invoice.

This is the invoice posting. Note the Payment Term and the Baseline Date.

Customer's dunning info

Dunning levels configuration

Okay so this is my dunning run.

Dunning scheduled. No notices generated!

This is the log. Account D 100001 is blocked by dunning run 20141031 (no Identification? is that normal?)

This is the dunning run which has caused the block. Dunning run already performed.

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member664754
Discoverer
0 Kudos

For Additional users ,

Before you run any deletion please try just below note first:

2574934 - F150: Deletion of MAHNS for successfully printed dunning notices

BR

Former Member
0 Kudos

Hi Chin,

This is answered many times in the Forum.

Please check if the customer has any entries in the Table MAHNS. If yes, delete the entries from this table and then try again.

Please check the below SAP notes

12896: Delete Lock entries in MAHNS

BR

Amitash

Former Member
0 Kudos

Dear,

I have no authorization for that. the delete option is grayed out.

Can I do it via a T-code?

What is the difference between dunning lock and dunning block? As you can see up there, there is no block.

former_member229024
Contributor
0 Kudos

Hi Chin,

Dunning Block is the customer/vendor shouldn't be included in dunning run. This field can be found in Correspondance tab in K/D master data.

The issue in discussion, is out of number of customers dunned in your dunnng run , One customer with id 100001 is already entered in another dunning run (i.e blocked by another dunning run). This can be found in table MAHNS ( Provide customer id in Account field). either you can remove the customer from another dunning run or remove the customer from above dunning run and execute another run.

Cheers,


Former Member
0 Kudos

Hello Chin,

Dunning Block is to block customer /Vendor to be included in the Dunning Run.

Dunning Lock is that the customer / Vendor is locked by another Run.

You Need to create the Report as per SAP NOTE 186095 to delete the Locked entries in MAHNS table. There is no specific Transaction.

Hope that helps.

BR

Amitash

Former Member
0 Kudos

Dear Chin,

In the dunning run which caused the block 20141031, 6 dunning notices were generated but only 5 were printed. In the detailed Error log, you should get the reason why one dunning notice was not printed.

I think this is the cause why you cannot dun the customer at present.

All dunning notices from the previous run have to be printed first.

KInd regards