Frequent Error Messages during Asset Accounting data migration to S/4HANA

[Jennie_Qi]

Frequent Error Messages during Asset Accounting data migration to S/4HANA

During the conversion of an ERP solution to SAP S/4HANA, several frequent errors may occur in Asset Accounting (FI-AA) data migration. Below is a summary of the most common errors and their resolutions:

Error FINS_RECON761:

• Possible Causes:
• If the error comes up in phase R25 and the difference is very small for the field NAFAP in tables FAAV_ANLC_ORI and FAAV_ANLC, it is due to rounding and can be ignored.
• Very often, the error is closely related to error message FINS_RECON795 in phase R21, when there is a mismatch between line Items ANEP/ ANEA and Totals ANLC for certain assets. In this case, the inconsistency existed in the source ERP, already and can be due to different reasons (wrong handling, software bugs etc.)
• Recommendation:

1. Use program FINS_MIG_AA_CHECK_RC45 for detailed FI-AA error checks.

1. Compare records in the source ERP system between ANLC and ANEP/ANEA tables to identify if there are any inconsistencies or not.
2. If no inconsistencies are found in 1 and If error is in phase R25 : check the NAFAP field to see if there are small differences for tables FAAV_ANLC_ORI and FAAV_ANLC. If small differences are found, this error can be accepted.  As these differences are due to rounding done by the system when using Depreciation Methods with Base Value equal to Acquisition or Replacement, because of a more precise data type used for the calculation in S/4 HANA. This is explained in SAP KBA 2328351 - FINS_RECON 761 for small NAFAP differences.
3. If the error occurs in Phase R25 and you are using a leasing solution: Check SAP KBA 3442610 - Error FINS_RECON761 occurred in step R25 during data migration to S/4HANA - SAP for Me for leasing solutions.
4. If error is in phase 24: Refer to SAP Notes 2514510 - Data Migration: FINS_RECON 761 in step R24 - SAP for Me, 2532471 - No updates in migration process step DLT_AA or during Balancy Carry Forward - SAP for Me, 2526882 - FINS_RECON 761 in step R24 for fiscal years with archived depreciation (ANLP) - SAP for Me, 2767354 - Error message FINS_RECON 761 ("Mismatched balance for ANLC") in migration step R24 - SAP f....
5. If old fiscal years are affected, archiving could be considered as an option, since re-opening of old fiscal years is most of the times no option for customer.
6. If unresolved, create a SAP incident to contact SAP (component FIN-MIG-AA).
7. For more information, refer to SAP Note 2714344 - Financial data migration to SAP S/4HANA: Most frequent Error Messages – Information and Re...

Errors FINS_RECON741, 743, 744, 771, 772

Possible Causes:

• Data not completely migrated in phase MUJ because of e.g.: FI-AA customizing in SAP S/4HANA is not complete (e.g. missing account determinations) or Program error etc.
• Very often there are other error messages for the same assets in earlier phases (e.g. FINS_RECON793 in phase R21) because the data is inconsistent in the source system
• Error message can happen in context of migration of group assets before the SAP S/4HANA Conversion. Refer to SAP Note 2508546. Errors are displayed for identical assets. The affected assets are assigned to a group asset in the reported area or are themselves group assets.
• Recommendation:

1. Use program FINS_MIG_AA_CHECK_RC45 for detailed FI-AA error checks
2. In case of group assets, check the values for assets (group and individual assets ) with errors and compare them with the values in ECC system.  If amounts are correct and the only difference is in LNRAN for individual assets, refer to note 2508546 - Error messages in context of migration of group assets - SAP for Me
3. If the errors are due to inconsistency between group assets and individual assets in other scenarios, analyze and check further and resolve these inconsistencies before migration.
4. As a remark, group assets are available in S/4HANA after migration but after the end of 2025, group assets functionality will no longer be supported by SAP. Further information can be found in 3014869 - S4TWL - Group Assets - SAP for Me
5. Check SAP Notes 2514510 and 2577469 are implemented
6. Check SAP Note 2785894 is implemented before the MUJ Phase execution
7. If the error message is for old fiscal years, consider archiving that old data before conversion.
8. If the issue persists, create SAP incident to contact SAP (component FIN-MIG-AA).

1. For more information, refer to SAP Note 2714344 - Financial data migration to SAP S/4HANA: Most frequent Error Messages – Information and Re...

Brought to you by the SAP S/4HANA Customer Care and RIG.