FI-AA Data Migration into S/4 HANA: FINS_RECON 795 '&1: Line Items ANEP/ANEA differs from Totals ANLC'

The error message is self explanatory and points out to mismatch of asset postings line items values stored in ANEP / ANEA tables with totals values in ANLC table.

First of all, consider the FYs listed in error message, if older than 10 years, recommendation is to archive errored out data, which is advised by SAP according to SAP note 3038014, for example.

Second, error message points out to existing data inconsistencies between asset line items and totals values for concerned assets / FYs / depreciation areas. These may be due to mismatch in planned or posted depreciation values (NAFAP, NAFAG field values) between ANEP and ANLC, i.e. causing the consecutive mismatch in asset NBV in asset explorer and Asset Accounting reports (Asset Balances, Asset History Sheet).

To be more precise, planned depreciation amount that wasn't posted due to different reasons (program bug, depreciation key OR depreciation area set- up and etc.) in ECC won't be migrated to S/4 HANA into ANLC / FAAV_ANLC tables, while still be available in FAAV_ANLC_ORI which, in turn, will trigger the 795 error during data migration. So, technically, you still have the unposted values available in S/4 HANA and, if required, build a separate CDS view for retrieving data from FAAV_ANLC_ORI for your internal reporting purposes.

It is possible to utilize these standard RACORR* programs to rebuild FI‑AA DB entries in ECC. However, if the inconsistency is legitimate, i.e. existing unposted depreciation amounts from previous FYs, then any corrections applied will be overwritten once the consecutive Balance Carryforward (BCF) run is executed. In general, I would be very precautious with usage of any Asset Accounting correction programs as they might potentially alter the BCF amounts of closed FYs.

So, if the errors occurred for closed FYs and archiving is not possible, recommendation is to acknowledge and accept the errors (in MUJ or R25 segments of FINS_MIG_STATUS t-code), as any corrections would alter the financial reports for already closed FYs.