How To Fix FDM_COLLECTION216 - Cleared residual items with reference to promise to pay

SAP Error Message - Details

• Message type: E = Error

• Message class: FDM_COLLECTION - SAP Collections Management

• Message number: 216

• Message text: Cleared residual items with reference to promise to pay

trados = docu -> fi -> fica

What causes this issue?

This clearing resulted in the creation of residual items for which
payments have since been received and updated in a promise to pay. The
clearing reset means that the items lose their reference to the invoice
and therefore also to the promise to pay.

System Response

The clearing reset is not permitted.

How to fix this error?

Check the clearing of the residual items.
First reset all clearings that have updated data in the promise to pay.
The system determined the following clearing documents:
&V1&

&V2&


&V3&


&V4&

If you do not want to reset the clearing above, you can withdraw the
promise to pay instead. Then reset clearing and enter the promise to pay
again.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDM_COLLECTION216 - Cleared residual items with reference to promise to pay ?

  The SAP error message FDM_COLLECTION216 typically relates to issues in the Financial Data Management (FDM) module, particularly in the context of collections and accounts receivable. This error message indicates that there are cleared residual items associated with a promise to pay, which can occur in various scenarios involving customer payments and open items.
  Cause:
  
  Cleared Residual Items: The error usually arises when there are cleared items in the system that are still linked to a promise to pay. This can happen if a customer has made a payment that partially clears an invoice, but there are still outstanding amounts that are not fully resolved.
  Inconsistent Data: There may be inconsistencies in the data related to customer accounts, such as incorrect postings or missing information that prevents the system from processing the promise to pay correctly.
  Configuration Issues: Sometimes, the configuration settings in the FDM module may not be set up correctly, leading to issues with how promises to pay are handled in relation to cleared items.
  
  Solution:
  
  Review Cleared Items: Check the customer account for any cleared items that are still linked to the promise to pay. You may need to manually clear or adjust these items to resolve the error.
  Adjust Promises to Pay: If the promise to pay is still valid, ensure that it is correctly reflecting the current outstanding amounts. You may need to update or recreate the promise to pay to align it with the current status of the account.
  Data Consistency Check: Run a consistency check on the customer account data to identify any discrepancies or issues that need to be addressed.
  Consult Documentation: Refer to SAP documentation or support resources for specific guidance on handling this error message, as there may be additional steps or considerations based on your system configuration.
  Contact SAP Support: If the issue persists after attempting the above solutions, consider reaching out to SAP support for further assistance. They can provide more detailed insights based on your specific system setup and the context of the error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL5N (Customer Line Item Display) to review customer account details and open items.
  SAP Notes: Check for any SAP Notes related to FDM_COLLECTION216, as these may provide patches or updates that address known issues.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users.
  
  By following these steps, you should be able to diagnose and resolve the FDM_COLLECTION216 error effectively.