Symptom
After migrating legacy asset values, the system prevents setting an asset deactivation date that falls before or on the legacy transfer (posting) date.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the Migration Cockpit and migrate legacy asset values, including takeover values and any retirement or movement lines.
- Post the legacy takeover so that the migrated values are recorded on the legacy transfer (posting) date.
- Open the migrated asset in the Manage Fixed Assets app.
- Attempt to set the asset Deactivation Date to a date earlier than or equal to the legacy transfer (posting) date.
- Observe the error — the system blocks the deactivation.
Cause
This is a system constraint. The deactivation date must be set to at least one day after the legacy transfer (posting) date. Since asset values are recorded on that date, an earlier deactivation would create an inconsistency in the depreciation calculation.
Resolution
This is the expected system behavior and not a defect. To deactivate the asset, set the deactivation date to a date that is at least one day after the legacy transfer (posting) date.
Keywords
asset accounting, deactivation date, legacy transfer date, migration cockpit, retirement posting, posting date, takeover date, depreciation area 01, group currency, ordinary depreciation, error message, mid-year migration, asset deactivation blocked , KBA , FI-FIO-AA-MD-2CL , Fiori Apps for Asset Master Data (Public Cloud) , Problem
SAP Knowledge Base Article - Public