Asset management: depreciation area missing after migration, asset values not updating in FI

ERP SAP S/4HANA
, , , , , , , ,
1

After our migration to S/4HANA 1909, we discovered that approximately 230 fixed assets are missing depreciation area 01 (book depreciation) assignments. These assets show correct values in the legacy ECC system, but in S/4HANA the depreciation area is blank when viewing asset master data in AS03.

The migration team used transaction ASMIG01 for the asset transfer, and the migration log showed successful completion with no errors. However, when finance ran the first depreciation posting run using AFAB, these assets were skipped:


Asset 100234567 - Depreciation Area 01 not found
Asset 100234589 - Depreciation Area 01 not found

The FI integration is also affected - asset values aren’t flowing to the balance sheet accounts correctly. This is blocking our month-end close for April. What could cause depreciation areas to be lost during migration?

2

Check the migration cockpit logs more carefully - look in table /1CADMC/A_LOG_MSG for detailed error messages that might not show in the summary. Filter by object type ‘ANLA’ and check for warning messages with category ‘W’. Also verify in transaction OAYZ that your asset classes have depreciation areas properly assigned in the S/4HANA system.

3

Did you run the asset data validation program RACUSTOM before the migration? Also check table ANLZ to see if the depreciation area records exist but aren’t displaying. Sometimes the issue is with the screen layout variant in transaction AS03 rather than missing data.

4

The depreciation key assignment issue suggests incomplete IMG configuration transfer. Run program RAIST_ASSET_CLASS_CHECK to identify all asset classes with incomplete depreciation area assignments. You’ll need to manually configure these in OAYZ before you can correct the affected assets. For the 230 assets already migrated, you’ll need to use mass change transaction AS02 or create a LSMW script to add the missing depreciation areas retroactively.

5

Here’s a comprehensive solution addressing all three focus areas:

Depreciation Area Assignment: The root cause is incomplete asset class configuration in S/4HANA. Follow these steps:

  1. First, compare ECC and S/4HANA configurations using transaction OAYZ. Export the depreciation area assignments for all asset classes from both systems and identify discrepancies.

  2. For asset class 3100 (and any others missing assignments), configure depreciation area 01 in OAYZ:

    • Asset class: 3100
    • Depreciation area: 01
    • Depreciation key: LIN (or your standard key)
    • Account determination key: Match your ECC setting

  3. Verify the chart of depreciation assignment in transaction OADB:


Company Code: 1000
Chart of Depreciation: 1US
Depreciation Area: 01 - Book Depreciation

Asset Master Data Update: For the 230 affected assets, don’t use mass change immediately. Instead:

  1. Run report RAIST_ASSET_CLASS_CHECK to get the complete list of affected assets and their asset classes.

  2. Create a correction LSMW project using object 0090 (Asset Master Record). Map these fields:

    • ANLA-ANLN1 (Asset number)
    • ANLA-BUKRS (Company code)
    • ANLZ-AFASL (Depreciation key for area 01)
    • ANLZ-NDJAR (Asset value date)

  3. Before loading, test with 5-10 assets using transaction AS02 to verify the depreciation calculation works correctly after adding the area.

  4. For each corrected asset, run transaction AFBN to post catch-up depreciation from the migration date to current date. This ensures your accumulated depreciation matches what it should be.

  5. Use transaction ABAA to verify that depreciation values match between ECC historical data and the recalculated S/4HANA values.

FI Integration: To restore proper asset-to-GL integration:

  1. Verify account determination in transaction AO90. Check that depreciation areas 01 has correct GL account assignments:

    • Accumulated depreciation: Account 108000
    • Depreciation expense: Account 660000
    • Asset acquisition: Account 107000

  2. After correcting the asset master data, run program RAPOST00 with test mode enabled to simulate the depreciation postings for the affected assets. Review the posting simulation report carefully.

  3. Execute the actual depreciation run using AFAB for the current period only. Use processing variant “RESTART” to include previously skipped assets.

  4. Reconcile asset subledger to GL using transaction ABST2. This will identify any remaining discrepancies between asset values and GL balances.

  5. For the missed April depreciation, you’ll need to run AFAB with “Repeat run” option and specify April as the posting period. This requires the period to still be open in FI.

  6. Create a monitoring report using transaction SQVI based on table ANLC (Asset Values) joined with ANLA (Asset Master) to identify any future assets with missing depreciation area assignments before they cause posting issues.

Important: Before executing the correction steps in production, test the entire process in your QA system with a copy of production data. Document the exact steps and timing because this will affect your financial statements retroactively.

6

Good catch on the migration logs. I found warnings in /1CADMC/A_LOG_MSG indicating “Depreciation area determination failed for asset class 3100”. When I checked OAYZ, asset class 3100 exists but the depreciation key assignment is missing for area 01. This asset class covers most of our machinery assets, which explains why so many are affected.