Data consistency is a major success factor for an efficient and trouble-free system conversion to S/4HANA. Fortunately, SAP has recently rolled out new tools that can be implemented in your ERP system to discover and potentially correct these inconsistencies before a conversion project starts. In my recent blogs S/4HANA_System Conversion_ Finance Data Consistency checks and Finance Consistency Checks: FIN_CORR_MONITOR I described the new tools available to identify inconsistencies in General Ledger data. In November 2020 SAP has now also released new tools to identify data inconsistency problems for Fixed Assets. These new tools enable new transaction codes in your ERP system that can used to execute reports that identify Asset related data inconsistencies.
A key difference between the new General Ledger tools and the Fixed Asset tools is that the Fixed Asset tools do not yet include any capabilities to correct discovered inconsistencies. The lack of an automated self-correction feature is likely due to the complexity of Fixed Asset logic, and there is no current commitment from SAP to deliver such tools for Fixed Assets anytime soon. Therefore after detection of Fixed Asset inconsistencies, project teams will have to identify correction notes** or solicit SAP Support’s help for resolution assistance.
How to install and execute the new Fixed Asset Consistency Checks
The new Fixed Asset Consistency Checks consist of two new transaction codes: FIN_AA_CORR_RECON & FIN_AA_CORR_DISPLAY. Both transactions are executed in the source ERP system prior to conversion.
FIN_AA_CORR_RECON checks and analyzes fixed asset data and verifies the preconditions for conversion.
The FIN_AA_ CORR_RECON process focuses on 29 potential errors found on the reconciliation steps R21, R22, R23, R25 and R25 inside of FINS_MIG_STATUS _ Migration Monitor.
And to display the results run transaction FIN_AA_CORR_DISPLAY
To activate these reports in the ECC system follow SAP note 2896400 – “Reconciliation of Asset Accounting Inconsistencies in ECC prior to S/4HANA Conversion”
How to resolve detected inconsistencies
SAP Note 2714344 – “Financial data migration to SAP S/4HANA: Most frequent Error Messages – Information and Recommendation” was created to provide a convenient source of project experiences to help resolve known issues. I have extracted the Fixed Assets correctable errors from this note with information on the correction strategy recommendations, but please check to most recent version of the note when researching a specific issue:
** 2714344 – Financial data migration to SAP S/4HANA: Most frequent Error Messages – Information and Recommendation
Migration phase | Application component | Error message | Performed checks | Root cause examples | Potential impact | Recommendation |
R23: Check Migration of Journal Entry | FI-AA | FINS_RECON 741 |
Error text: NO ENTRY in COMPATIBILTY VIEW ITEM FOR ENTRY IN ORIGINAL TABLE (ANEP) Functional check: Check existence of entry in original view for ANEP (FAAV_ANEP_ORI) v. compatibility view (FAAV_ANEP) |
FI-AA customizing in SAP S/4HANA is not complete (e.g. missing account determinations) Program error etc.
|
1. Mismatch between ANEP values (in ERP and SAP S/4HANA) |
1. Check that the SAP Note 2514510 is implemented 2. Use analysis program FINS_MIG_AA_CHECK_RC45 to analyze the origin for the error messages in detail. 3. If the error message is for old fiscal years, consider |
R23: Check Migration of Journal Entry | FI-AA | FINS_RECON 744 |
Error text: MIMATCHED AMOUNT &2 (ANEP) Functional check: Checks for mismatch in amounts between compatibility view (FAAV_ANEP) and original view for ANEP (FAAV_ANEP_ORI) |
|
1. Mismatch between ANEP values (in ERP and S/4) 2. There might be related error message FINS_RECON781 in phase R24 |
1. In case of group assets, Check the SAP Note 2508546 2. If the error message is for old fiscal years, consider archiving that old data before conversion. 3. Use analysis program FINS_MIG_AA_CHECK_RC45 to analyze the origin for the error messages in detail. |
R24: Check Migration of Balances R25: Check Initial Depreciation Calculation |
FI-AA | FINS_RECON 761 |
Error text: MISMATCHED BALANCE FOR ANLC Functional check: Compare the balance of the original table ANLC (can be checked in SAP S/4HANA system via view FAA_ANLC_ORI ) and compatibility view (FAAV_ANLC) In phase R25, the check from R24 is repeated after the initial depreciation calculation has been made in the predecessor phase AFA |
|
1. Typically the inconsistency existed in the source ERP system, already. 2. Refer to the long-text of error message FINS_RECON795 |
1. The FI-AA errors can be checked more in detailed by help of program FINS_MIG_AA_CHECK_RC45 2. If error is in phase R25, check the KBA 2328351 for relevance (small rounding differences in NAFAP) 3. If error is in phase R24, check SAP Note 2514510, 2532471, 2526882 and 2767354 for relevance 4. 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 customers 5. Otherwise, contact SAP (component FIN-MIG-AA) |
R24: Check Migration of Balances | FI-AA | FINS_RECON 763 |
Error text: RECONCILIATION ACCOUNT &2: TOTAL WITHOUT ASSET ASSIGNMENT Functional check: Check that the total of all non-asset lines posted on the reconciliation account is 0,- |
|
1. Inconsistency between FI-GL and FI-AA 2. If the inconsistency exists in the source system is not corrected there and is accepted in FINS_MIG_STATUS, this cannot be corrected any longer in the migrated system afterwards |
1. Check that SAP Note 2480922 is implemented 2. Follow the steps explained in the FIN Conversion guide attached to SAP Note 2332030 and make sure all the period end closing activities and reconciliation tasks are carried out in the source system before the SAP S/4HANA conversion 3. Error message FINS_RECON763 might be unjustified, if the migration of a legacy data transfer was carried out in the current year. Refer to SAP Note 2346879 for more details in this case 4. Otherwise, contact SAP (component FIN-MIG-AA) |
R24: Check Migration of Balances | FI-AA | FINS_RECON 764 |
Error text: ANLC VALUES WITHOUT GENERAL LEDGER ASSIGNMENT IN THE OPEN YEAR Functional check: Check, that all annual values in ANLC are covered by the balance carryforward year of the general ledger. |
|
1. Mismatch between GL and FI-AA. Reconciliation has to be made before conversion |
1. Make sure SAP Note 2670612 is implemented to see a long-text of the error message 2. In the original system, make sure that the balance carryforward to the identical years has been performed consistently in asset accounting and in the general ledger for all ledgers 3. Before the SAP S/4HANA Conversion, run the reconciliation between FI-GL and FI-AA in the source system. Follow the steps in the FIN Conversion guide attached to SAP Note 2332030 4. Otherwise, contact SAP (component FIN-MIG-AA) |
R24: Check Migration of Balances | FI-AA | FINS_RECON 766 |
Error text: MISMATCHED BALANCE FOR ANLP Functional check: Compare balance of original tableANLP (view FAAV_ANLP_ORI) and compatibility view (FAAV_ANLP) |
|
1. Differences in Periodic Asset Values between ERP and S/4HANA |
1. The FI-AA errors can be checked more in detailed by help of program FINS_MIG_AA_CHECK_RC45 2. If the error message is for old fiscal years, consider archiving that old data before conversion 3. If the error are raised for closed fiscal years, check if the aggregated totals per fiscal year between original ANLP and ACDOCA view are the same. In this case there would only be a difference in the posting periods. In this case the error message could be ignored/accepted 4. Check that the SAP Note 2514510 is implemented 5. Otherwise, contact SAP (component FIN-MIG-AA) |
R21: Reconciliation of Transactional Data | FI-AA | FINS_RECON 769 |
Error text: MISMATCH BETWEEN TRANSACTION TYPE IN ANEP AND PROVIDED ANEA FILEDS Functional check: See long-text of error message-and explanation in SAP Note 2424657 |
|
1. Potential runtime errors after the migration in subsequent processes such as intracompany transfers or reversals |
1. If the error message is for old fiscal years, consider archiving that old data before conversion 2. If the relevant asset has been retired meanwhile, the errors can be ignored 3. Only in case the error is for the open year or year before, contact SAP (component FIN-MIG-AA) |
R23: Check Migration of Journal Entry | FI-AA | FINS_RECON 771 |
Error text: NO ENTRY IN COMPATIBILITY VIEW ITEM FOR ENTRY IN ORIGINAL TABLE ANEK Functional check: Check existence of entry in original view for ANEK (FAAV_ANEK_ORI) v. compatibility view (FAAV_ANEK) |
|
1. Mismatch between ANEK values (in ERP and SAP S/4HANA) |
1. Check that the SAP Note 2577469 is implemented 2. Check that the note 2785894 is implemented before the MUJ Phase execution 1. If the error message is for old fiscal years, consider archiving that old data before conversion |
R24: Check Migration of Balances | FI-AA | FINS_RECON 781 |
Error text: MISMATCHED BALANCE FOR ANEA Functional check: Compare balance of original tableANEA (FAAV_ANEA_ORI) and compatibility view (FAAV_ANEA) |
|
1. Depends on situation and root cause |
1. Use analysis program FINS_MIG_AA_CHECK_RC45 to analyze the origin for the error messages in detail 2. If the error occurs in case of group assets, Check the SAP Note 2508546 3. If the error message is for old fiscal years, consider archiving that old data before conversion 4. Otherwise, contact SAP (component FIN-MIG-AA) |
R21: Reconciliation of Transactional Data | FI-AA | FINS_RECON 793 |
Error text: NO ENTRY IN ORIGINAL TABLE ANEP FOR LEADING DEPR.AREA Functional check: The system checks whether at least one data record of the leading depreciation area exists for parallel depreciation areas in table ANEP (FAAV_ANEP_ORI) |
|
1. Depends on error situation 2. If not corrected, there might be a follow-up error message FINS_RECON 766 in the phase R24 |
1. Check the long-text of the error message and follow the recommendations given there and in the SAP Note 2144919 to get rid of the error message 2. Otherwise, contact SAP (component FIN-MIG-AA) |
R21: Reconciliation of Transactional Data | FI-AA | FINS_RECON 795 |
Error text: LINE ITEMS ANEP/ANEA DIFFERS FROM TOTALS ANLC Functional check: Aggregated values of line items in ANEP and ANEA do not match the totals in table ANLC |
|
1. Refer to error message long-text 2. In migration step R24 (Check Migration of Balances), the total of these migrated line items is compared with the former totals tables. If there was already a difference between the line item and the totals table in phase R21 (FINS_RECON795), this usually causes a mismatch. Error message FINS_RECON 761 is issued for the fixed asset and fiscal year in R24 then |
1. Use analysis program FINS_MIG_AA_CHECK_RC45 to analyze these error messages in detail 2. Refer to error message long-text |
MUJ: Data Migration into Unified Journal: Line Items and/or DLT: Data Migration into Unified Journal Entry: Aggregate Deltas |
FI-AA | FINS_FI_MIG 081 |
Error text: GL ACCOUNT NOT MAINTAINED FOR KTOPL & KTOGR & AFABE & TYPE Functional check: Check for missing account assignments in FI-AA customizing |
|
1. The relevant line items (in phase MUJ) or balances (in phase DLT) balances cannot not migrated correctly |
1. Make sure SAP Note 2581270 is implemented to have more information in the error message 2. Check the SAP Note 2678925 for possible solutions. Check the FI-AA account assignments in transaction AO90 3. Running check report RASFIN_MIGR_PRECHECK in the SAP S/4HANA system can also be helpful identifying missing/wrong FI-AA customizing 4. Otherwise, contact SAP (component FIN-MIG-AA) |
MUJ: Data Migration into Unified Journal: Line Items | FI-AA | FINS_FI_MIG 082 |
Error text: BALANCE SHEET ACCOUNT DETERMINATION MISSING FOR &1, &2, &3 AREA &4 Functional check: Check for missing balance sheet account assignments in FI-AA customizing |
|
1. The relevant line items cannot not migrated correctly |
1. Check the KBA 2678925 for possible solutions. That Note is related to error FINS_FI_MIG081, but the proposed steps to be checked in that Note are valid for FINS_MIG082 errors as well. Check the FI-AA account assignments in transaction AO90 2. Running check report RASFIN_MIGR_PRECHECK in the SAP S/4HANA system can also be helpful identifying missing/wrong FI-AA customizing 3. Otherwise, contact SAP (component FIN-MIG-AA) |
R21: Reconciliation of Transactional Data | FI-AA | ACC_AA 213 |
Error text: COCD &1: DATA FOR ASSET ACCOUNTING IS NOT ARCHIVED Functional check: Check if deactivated company codes have data: as they will not be migrated, data will be lost if not archived. |
|
1. If the data is neither archived nor the documents are migrated, it will be no longer possible to display documents in the future | 1. Check the long-text of the error message and the SAP Note 2406313 for the possible optio |
In conclusion, Fixed Assets data needs to be identified, analyzed and corrected in ECC system to fulfill the pre-conditions for a System Conversion to S/4HANA. In this blog post you learn about new transaction codes that will help with those activities and guide you during the process.
Hopefully this blog was helpful!
Please add in the comment section any other topics you think are valuable to have included in this blog post.
– Brought to you by the S/4HANA RIG