How To Fix 0D735 - | Doc. &1 dunned despite insufficient deposit coverage or coll. lock

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 735

• Message text: | Doc. &1 dunned despite insufficient deposit coverage or coll. 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 0D735 - | Doc. &1 dunned despite insufficient deposit coverage or coll. lock ?

  The SAP error message 0D735 indicates that a document (usually an invoice or a billing document) is being dunned (i.e., a reminder for payment is being sent) despite the fact that there is insufficient deposit coverage or a collection lock in place. This typically occurs in the context of accounts receivable and dunning processes.
  Cause:
  
  
  Insufficient Deposit Coverage: This means that the customer does not have enough deposit balance to cover the outstanding invoice amount. In SAP, deposits can be used to offset outstanding invoices, and if the deposit is insufficient, the system will raise this error.
  
  
  Collection Lock: A collection lock may be in place for the customer or the specific document, which prevents the dunning process from proceeding. This could be due to various reasons, such as a dispute, payment plan, or other internal controls.
  
  
  Solution:
  
  
  Check Customer Deposits: Verify the customer's deposit balance in the system. If the deposit is indeed insufficient, you may need to request additional payment from the customer or adjust the deposit accordingly.
  
  
  Review Collection Locks: Investigate if there are any collection locks on the customer account or the specific document. You can check the customer master data or the document status to see if there are any flags or indicators that prevent dunning.
  
  
  Adjust Dunning Parameters: If the dunning process is not supposed to occur under certain conditions (like insufficient deposits), you may need to review and adjust the dunning configuration settings in SAP. This can include dunning levels, thresholds, and other parameters.
  
  
  Consult with Finance Team: If you are unsure about the appropriate action, consult with your finance or accounts receivable team. They may have specific procedures in place for handling such situations.
  
  
  SAP Notes and Documentation: Check SAP Notes or the SAP Help Portal for any specific notes related to this error message. There may be patches or updates that address this issue.
  
  
  Related Information:
  
  Dunning Process: Understand the dunning process in SAP, including how it is configured and the various dunning levels.
  Customer Master Data: Review the customer master data for any flags or settings that might affect dunning.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FD10N (Customer Balance Display), F150 (Dunning), and FBL5N (Customer Line Item Display) to investigate the issue further.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights or similar experiences from other users.
  
  By following these steps, you should be able to identify the root cause of the error and take appropriate action to resolve it.