cancel
Showing results for 
Search instead for 
Did you mean: 

Dunning lock at document level did not exclude document

Former Member
0 Kudos

Converted items were updated with dunning lock effective 04/01/2012 until 12/31/9999. Dunning ran on 04/02/2012 with issue date of 04/02/2012.  These converted items were not excluded even though the documents have dunning lock at the document level.  What would be the reason why this happened?

Accepted Solutions (0)

Answers (2)

Answers (2)

william_eastman
Advisor
Advisor
0 Kudos

GM:

Check your document - and find where the locks were entered.  The lock field on DFKKOP is not used.  The lock must be stored in DFKKLOCKS.  So maybe your migration was not correctly done.

regards,

bill.

Former Member
0 Kudos

Hi, Lock not in DFKKOP.  The lock is in DFKKLOCKS with lock category 02 (Line Item) and process 01 (Dunning) but it did not work.

Thanks.

ivor_martin
Active Contributor
0 Kudos

Hi,

Check to see if there is a Payment lock along with an Incoming Payment Method either on the documents in question or on the Contract Accounts in question.

If so, the item could be  ignoring  the Dunning Lock.

Regards,

Ivor M.

Former Member
0 Kudos

Hi,

Please check the below thing.

In FPL9 open the particular dunning item, go to the "Dunn Data" tab, there is a field called "DunnLockReason", next to this field there is "Right Direction" arrow, click the same, and check the validity date, check the other details.

May be you can find something useful.

Regards

Sachin