How To Fix FKKCOLL128 - Correspondence for invoice &2 for document &1 already exists

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 128

• Message text: Correspondence for invoice &2 for document &1 already exists

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 FKKCOLL128 - Correspondence for invoice &2 for document &1 already exists ?

  The SAP error message FKKCOLL128 indicates that there is an attempt to create correspondence for an invoice that has already been processed. This typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module, where correspondence (such as reminders, invoices, or statements) is generated for customer accounts.
  Cause:
  The error arises when the system detects that correspondence for the specified invoice (document &1) has already been created for the specified document number (&2). This can happen due to:
  
  Duplicate processing attempts for the same invoice.
  Manual attempts to generate correspondence for an invoice that has already been processed.
  System settings or configurations that prevent multiple correspondences for the same document.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Correspondence:
  
  Verify if correspondence for the specified invoice already exists. You can do this by checking the correspondence history for the document in question.
  
  
  
  Review Correspondence Settings:
  
  Check the configuration settings in the SAP system related to correspondence. Ensure that the settings allow for the desired correspondence types and that there are no restrictions preventing the generation of new correspondence.
  
  
  
  Avoid Duplicate Processing:
  
  Ensure that the process generating the correspondence is not being triggered multiple times for the same invoice. This may involve reviewing the workflow or batch job that is responsible for generating correspondence.
  
  
  
  Use Different Correspondence Type:
  
  If you need to send additional correspondence, consider using a different correspondence type that is allowed for the same invoice.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to the FKKCOLL128 error for any specific guidance or updates that may apply to your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP support for further assistance. They may provide insights based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like FPL9 (Display Correspondence) or FPL1 (Create Correspondence) to manage and review correspondence.
  SAP Notes: Check for relevant SAP Notes that may address this specific error or provide patches/updates.
  User Exits and BAdIs: If custom logic is involved in the correspondence generation, review any user exits or BAdIs that may affect the process.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.