How To Fix FKKCOLL120 - Collection assignment incorrect: collection unit &1 does not exist

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 120

• Message text: Collection assignment incorrect: collection unit &1 does not exist

What causes this issue?

The assignment of the collection payment &V2& contains an error:
Collection unit &V1& does not exist.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the payload and check with the collection agency, if necessary.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKKCOLL120 - Collection assignment incorrect: collection unit &1 does not exist ?

  The SAP error message FKKCOLL120 indicates that there is an issue with the collection assignment in the SAP system. Specifically, it states that the collection unit specified (denoted as &1 in the error message) does not exist. This error typically arises in the context of contract accounts receivable and payable (FI-CA) when trying to process a collection assignment.
  Cause:
  
  Non-Existent Collection Unit: The collection unit referenced in the transaction does not exist in the system. This could be due to a typo, or the collection unit may have been deleted or not created.
  Incorrect Configuration: The configuration settings for the collection units may not be set up correctly, leading to the system not recognizing the specified unit.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables that manage collection units.
  
  Solution:
  
  
  Verify Collection Unit: Check the collection unit number that is being referenced in the transaction. Ensure that it is correctly entered and exists in the system.
  
  You can do this by navigating to the relevant transaction in SAP (e.g., using transaction code OBD2 for collection unit configuration) and checking if the collection unit is listed.
  
  
  
  Create or Restore Collection Unit: If the collection unit does not exist, you may need to create it. This can be done through the configuration settings in SAP.
  
  Use transaction code OBD2 to create a new collection unit if necessary.
  
  
  
  Check Configuration Settings: Review the configuration settings for collection units to ensure they are set up correctly. This includes checking the assignment of collection units to the relevant organizational units.
  
  
  Data Consistency Check: Run data consistency checks to identify any discrepancies in the database that may be causing the issue. This can involve checking related tables for missing or incorrect entries.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on managing collection units and resolving related errors.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if it involves complex configuration or data issues.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBD2 (for collection unit configuration) and FQEVENT (for managing collection events).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to access and modify collection units in the system.
  
  By following these steps, you should be able to identify and resolve the issue related to the FKKCOLL120 error message in SAP.