How To Fix FINS_RECON330 - CoCd &1: Check of clearing information started at &2 and ended at &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 330

• Message text: CoCd &1: Check of clearing information started at &2 and ended at &3

What causes this issue?

Check of clearing information in FI-documents was executed in this
system.

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?

If inconsistencies concerning this check of clearing information
occurred, then these errors can be corrected by program
'FIN_CORR_MIG_ERROR_SFIN' <ZH>in the source system (i. e. your
productive system): </>
If you want to correct inconsistencies concerning clearing information
found in migration to S/4HANA Finance, then you have to start program
FIN_CORR_MIG_ERROR_SFIN in the source system. The inconsistencies which
have to be corrected are determined by a RFC-call from the source system
to this system. For more information, read the program documentation of
program FIN_CORR_MIG_ERROR_SFIN in the source system.
This procedure of correction in the source system will ensure that these
inconsistencies will not occur in future test migrations any more.

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 FINS_RECON330 - CoCd &1: Check of clearing information started at &2 and ended at &3 ?

  The SAP error message FINS_RECON330 typically relates to issues encountered during the reconciliation process in financial accounting, particularly when dealing with clearing accounts in a specific company code (CoCd). This error indicates that there was a problem during the check of clearing information for a specified time period.
  Cause:
  
  Data Inconsistencies: There may be inconsistencies in the clearing data for the specified company code. This could be due to missing or incorrect entries in the clearing accounts.
  Configuration Issues: Incorrect configuration settings in the financial accounting module may lead to issues during the reconciliation process.
  Timing Issues: The time period specified for the reconciliation may not align with the data available in the system, leading to discrepancies.
  Locked Entries: If there are locked entries in the database or if the system is in a state that prevents access to certain data, this could trigger the error.
  Authorization Issues: The user may not have the necessary authorizations to perform the reconciliation check.
  
  Solution:
  
  Check Clearing Data: Review the clearing data for the specified company code and time period. Ensure that all entries are correct and complete.
  Reconcile Manually: If automated reconciliation fails, consider performing a manual reconciliation to identify discrepancies.
  Review Configuration: Check the configuration settings in the financial accounting module to ensure they are set up correctly for the company code in question.
  Check Time Period: Verify that the time period specified for the reconciliation is correct and that there are no gaps in the data.
  Unlock Entries: If there are locked entries, work with your SAP Basis team to unlock them or resolve any issues preventing access.
  Authorization Check: Ensure that the user performing the reconciliation has the necessary authorizations to access the required data.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), or FBL3N (G/L Account Line Item Display) to investigate the entries in the clearing accounts.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to financial reconciliation processes for best practices and guidelines.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.