How To Fix FINS_RECON720 - &1: Check of CO prior to migration started at &2 and ended at &3

FINS_RECON720 - Overview

• Message type: E = Error

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

• Message number: 720

• Message text: &1: Check of CO prior to migration started at &2 and ended at &3

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 FINS_RECON720 - &1: Check of CO prior to migration started at &2 and ended at &3 ?

  The SAP error message FINS_RECON720 typically relates to issues encountered during the reconciliation process in the context of financial data migration, particularly when moving data from one system to another or during system upgrades. This error indicates that there was a check of Controlling (CO) data prior to migration, and it provides timestamps for when the check started and ended.
  
  Cause:
  
  Data Inconsistencies: The error may arise due to inconsistencies or discrepancies in the CO data that need to be resolved before migration can proceed.
  Missing Data: Required CO data might be missing or incomplete, which can trigger this error.
  
  Configuration Issues: There may be configuration settings in the CO module that are not aligned with the requirements for migration.
  Authorization Issues: Lack of proper authorizations for the user executing the migration can also lead to this error.
  
  
  Solution:
  
  Check Logs: Review the detailed logs generated during the migration process to identify specific issues or inconsistencies in