How To Fix AY013 - Depreciation simulation data deleted due to change of company code

SAP Error Message - Details

• Message type: E = Error

• Message class: AY - Deprec. simulation - maint. module (AIPS) /gen. master data

• Message number: 013

• Message text: Depreciation simulation data deleted due to change of company code

What causes this issue?

The change of the company code &V2& to &V1& resulted in two different
charts of depreciation. Therefore, the system deleted the depreciation
simulation data you created.

System Response

The system also carried out the change of company code for
the depreciation simulation data. When you save, the depreciation
simulation data you entered for company code &V2& is not stored.

How to fix this error?

If you need the depreciation simulation parameters, call up the
screen for maintaining the depreciation parameters.
You can then maintain the depreciation simulation data for your
new company code.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AY013 - Depreciation simulation data deleted due to change of company code ?

  The SAP error message AY013 indicates that depreciation simulation data has been deleted due to a change in the company code. This typically occurs when an asset is transferred from one company code to another, and the system needs to ensure that the depreciation calculations are accurate and relevant to the new company code.
  
  Cause:
  
  Change of Company Code: The primary cause of this error is the transfer of an asset from one company code to another. When this happens, the system deletes any existing depreciation simulation data that is no longer applicable to the new company code.
  Inconsistent Data: If there are inconsistencies in the asset master data or if the asset is not properly configured for the new company code, it can lead to this error.
  
  Configuration Issues: Incorrect configuration in the asset accounting settings related to company codes can also trigger this error.
  
  
  Solution:
  
  Check Asset Transfer: Ensure that the asset transfer process