How To Fix FKKCOLL129 - Correspondence already exists for dunning notice for document &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKCOLL - Submission to Ext.Collection Agency/Legal Dunning Procedure

• Message number: 129

• Message text: Correspondence already exists for dunning notice for document &1

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 FKKCOLL129 - Correspondence already exists for dunning notice for document &1 ?

  The SAP error message FKKCOLL129 indicates that there is already existing correspondence for a dunning notice related to a specific document. This typically occurs in the context of the SAP Convergent Charging or SAP Contract Accounts Receivable and Payable (FI-CA) modules, where dunning processes are managed.
  Cause:
  The error arises when you attempt to create or send a dunning notice for a document that has already had correspondence generated. This is a safeguard to prevent duplicate dunning notices from being sent for the same document, which could lead to confusion for customers and potential compliance issues.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Correspondence:
  
  Review the correspondence history for the specific document (indicated by &1 in the error message). You can do this by navigating to the relevant transaction in SAP and checking the dunning history or correspondence logs.
  
  
  
  Identify the Dunning Notice:
  
  If you need to resend a dunning notice, check if the existing correspondence can be reissued or if it needs to be canceled first.
  
  
  
  Adjust Dunning Parameters:
  
  If the dunning process needs to be adjusted (for example, if the dunning levels or parameters have changed), you may need to modify the dunning run settings or the customer account settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files for specific instructions on handling dunning notices and correspondence.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide guidance based on your specific configuration and business processes.
  
  
  
  Related Information:
  
  Dunning Process in SAP: Understand how the dunning process works in SAP, including the different dunning levels and how correspondence is generated.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FKK_DUNN (Dunning History) to manage dunning notices effectively.
  Customization: Review any customizations in your SAP system that may affect the dunning process, as these can sometimes lead to unexpected behavior.
  
  By following these steps, you should be able to address the FKKCOLL129 error and manage your dunning notices effectively.