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

0D735 - Overview

• 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,