How To Fix 0D709 - > Document &1 dunned in spite of payment lock

SAP Error Message - Details

• Message type: E = Error

• Message class: 0D - FS-CD General Messages

• Message number: 709

• Message text: > Document &1 dunned in spite of payment lock

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 0D709 - > Document &1 dunned in spite of payment lock ?

  The SAP error message 0D709 indicates that a document has been dunned (i.e., a reminder for payment has been issued) despite the fact that there is a payment lock in place. This situation can arise in the context of accounts receivable and accounts payable processes within SAP.
  Cause:
  
  Payment Lock Not Recognized: The payment lock may not be properly recognized by the dunning program. This can happen if the lock is not set correctly or if there are inconsistencies in the document status.
  Dunning Procedure Configuration: The dunning procedure may be configured in such a way that it does not take payment locks into account.
  Timing Issues: If the payment lock was applied after the dunning run was executed, the dunning program may not be aware of the lock.
  Document Status: The document may have been in a status that allows dunning despite the payment lock.
  
  Solution:
  
  Check Payment Lock: Verify that the payment lock is correctly set on the document. Ensure that the lock is active and has been applied properly.
  Review Dunning Configuration: Check the dunning procedure settings in the configuration. Ensure that the dunning program is set to respect payment locks.
  Re-run Dunning Program: If the payment lock was applied after the dunning run, consider re-running the dunning program to see if the document is excluded from dunning.
  Document Status Review: Check the status of the document in question. If it is in a state that allows dunning, you may need to change its status or address any underlying issues.
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message or provide patches or updates that could resolve the issue.
  
  Related Information:
  
  Dunning Process: Understand how the dunning process works in SAP, including the configuration of dunning levels and the criteria for dunning.
  Payment Lock Mechanism: Familiarize yourself with how payment locks are implemented in SAP and their intended purpose.
  Transaction Codes: Use transaction codes like F150 (Dunning) to manage dunning runs and FB03 (Display Document) to view document details.
  SAP Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it appears to be a bug or a configuration issue that cannot be resolved through standard procedures.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to prevent it from occurring in the future.