How To Fix FINS_RECON790 - &1: Check of FI-AA tables before migration started at &2 and ended at &3

FINS_RECON790 - Overview

• Message type: E = Error

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

• Message number: 790

• Message text: &1: Check of FI-AA tables before 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_RECON790 - &1: Check of FI-AA tables before migration started at &2 and ended at &3 ?

  The SAP error message FINS_RECON790 typically indicates an issue related to the reconciliation of Financial Accounting (FI) and Asset Accounting (AA) tables during a migration process. This error suggests that there was a problem when checking the FI-AA tables before the migration started and provides timestamps for when the check began and ended.
  
  Cause:
  
  Data Inconsistencies: The most common cause of this error is inconsistencies or discrepancies in the data between the FI and AA tables. This can occur due to incomplete postings, missing entries, or incorrect configurations.
  
  Configuration Issues: Incorrect settings in the configuration of the FI and AA modules can lead to reconciliation issues.
  Migration Preparation: If the system is not properly prepared for migration, such as not having the necessary data checks or validations completed, this error may arise.
  Custom Developments: Any custom developments or modifications in the FI or AA areas that do not align with standard processes can also lead