How To Fix FINS_FI_MIG098 - asset reconciliation account &1 &2 is inconsistent in year &3

FINS_FI_MIG098 - Overview

• Message type: E = Error

• Message class: FINS_FI_MIG - SAP S/4HANA Finance: Data Migration

• Message number: 098

• Message text: asset reconciliation account &1 &2 is inconsistent in year &3

What causes this issue?

The G/L total for account &V2& in company code &V1& is inconsistent in
fiscal year &V3&. There is a difference of &V4& in G/L total of account
&V2& and asset management total of this account.

System Response

The balance carry forward will exclude asset management accounts until
the balance of all asset reconciliation accounts is consistent.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

FINS_FI_MIG098 - Details

• The SAP error message FINS_FI_MIG098 indicates that there is an inconsistency in the asset reconciliation account for a specific asset in a given year. This error typically arises during the migration or reconciliation process, particularly when transitioning to a new system or during year-end closing activities.
  
  Cause:
  
  
  Inconsistent Data: The asset reconciliation account specified in the error message does not match the expected values in the system. This could be due to:
  
  Missing or incorrect configuration in the asset accounting settings.
  Data inconsistencies between the asset master records and the general ledger.
  Changes in account assignments that were not properly reflected in the asset records.
  
  
  
  Migration Issues: If you are migrating data from an older system to SAP S/4HANA or another version, there may be discrepancies in how asset data was transferred.
  
  
  Posting Errors: Incorrect postings to the asset reconciliation account can lead to inconsistencies, especially if manual adjustments were made without proper documentation.
  
  
  
  Solution:
  
  
  Check Configuration: Verify the