How To Fix AY012 - Co. code & was transferred to depr. simulation data. Please check.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 012

• Message text: Co. code & was transferred to depr. simulation data. Please check.

What causes this issue?

The new company code &V1& was taken over into the present depreciation
simulation data. The previous company code was &V2&.
The change of company code could be carried out, since the two company
codes have the same chart of depreciation.

System Response

The system also carried out the change of the company code for the
depreciation simulation data. When you save, the depreciation
simulation data will also be saved for the new company code.

How to fix this error?

Nonetheless, you should check the depreciation simulation parameters:
1. If the old and the new company codes use different currencies, you
should adapt any existing scrap value accordingly. You should also be
aware of this regarding the group currency.
2. If the period versions are not the same, you should adapt the
depreciation start date, which would have changed according to the
depreciation start rule.
Therefore, you should check the maintenance of the depreciation
simulation parameters.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AY012 - Co. code & was transferred to depr. simulation data. Please check. ?

  The SAP error message AY012 indicates that there is an issue with the transfer of company code data to depreciation simulation data. This typically occurs in the context of Asset Accounting (FI-AA) when there are inconsistencies or issues with the configuration or data related to asset management.
  Cause:
  
  Configuration Issues: There may be a misconfiguration in the asset accounting settings, particularly related to the company code or depreciation areas.
  Data Inconsistencies: There could be inconsistencies in the asset master data or the related financial data that prevent the system from transferring the necessary information.
  Missing Data: Required fields or data may be missing in the asset master record or in the configuration settings for the company code.
  Authorization Issues: The user may not have the necessary authorizations to perform the action related to the company code and depreciation simulation.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for the company code in the Asset Accounting module. Ensure that all necessary settings are correctly defined.
  
  Transaction Code: OAOA (for company code settings)
  Transaction Code: OAYZ (for depreciation areas)
  
  
  
  Review Asset Master Data: Check the asset master records for any missing or incorrect information. Ensure that all required fields are filled out correctly.
  
  Transaction Code: AS02 (to change asset master data)
  
  
  
  Run Consistency Checks: Use the SAP standard reports to check for inconsistencies in asset accounting data.
  
  Transaction Code: ABAVN (for asset transfer)
  Transaction Code: ABUMN (for asset transfer)
  
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform actions related to asset accounting and company code settings.
  
  
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message. SAP Notes often provide patches or additional guidance for known issues.
  
  
  Debugging: If the issue persists, consider debugging the process to identify the exact point of failure. This may require assistance from a technical consultant.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in Asset Accounting, such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset).
  Documentation: Review SAP documentation related to Asset Accounting for best practices and configuration guidelines.
  SAP Community: Engage with the SAP Community or forums for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem continues after following these steps, it may be beneficial to consult with an SAP expert or your internal SAP support team for further assistance.