AA652 - SYST: Error when calculating last day in fiscal year.--> F1

SAP Error Message - Details

• Message type: E = Error

• Message class: AA - Messages for Asset Accounting

• Message number: 652

• Message text: SYST: Error when calculating last day in fiscal year.--> F1

What causes this issue?

While determining the last day of the period version &V2& of the
fiscal year &V1&, an error has occurred.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

This error could be produced from three different things:
The period version &V2& allocated to the company code has not been
created. In this case, you should create the period version.
The period version has been defined, but the allocation of calendar
dates to the fiscal periods has not been correctly performed, or in the
case of calendar-dependent period versions has not been completely
performed.
The calendar date &V1& is invalid. This is a system error. Contact your
Systems Specialist.

Error message extract from SAP system. Copyright SAP SE.

AnswerBot

• What is the cause and solution for SAP error message AA652 - SYST: Error when calculating last day in fiscal year.--> F1 ?

  The SAP error message AA652 ("SYST: Error when calculating last day in fiscal year") typically occurs in the Asset Accounting (FI-AA) module when the system encounters an issue while trying to determine the last day of the fiscal year for asset transactions. This can happen due to various reasons, including configuration issues, missing data, or inconsistencies in the fiscal year settings.
  Causes:
  
  Fiscal Year Configuration: The fiscal year may not be properly defined in the system. This includes settings in the controlling area or company code that do not align with the asset accounting settings.
  Missing or Incorrect Periods: The periods for the fiscal year may not be correctly set up, or there may be missing periods that prevent the system from calculating the last day of the fiscal year.
  Data Inconsistencies: There may be inconsistencies in the asset master data or transaction data that affect the calculation.
  System Settings: The system may not be configured to handle the specific fiscal year variant being used.
  
  Solutions:
  
  
  Check Fiscal Year Settings:
  
  Go to the configuration settings for the fiscal year in the SAP system (Transaction code: OB29 for fiscal year variant).
  Ensure that the fiscal year variant is correctly defined and that all periods are set up properly.
  
  
  
  Review Asset Master Data:
  
  Check the asset master records to ensure that all necessary fields are filled out correctly and that there are no inconsistencies.
  Use Transaction code: AS03 to display asset master data and verify the details.
  
  
  
  Check Periods:
  
  Ensure that all periods for the fiscal year are open and available for posting. You can check this in the period control settings (Transaction code: OB52).
  
  
  
  Run Consistency Checks:
  
  Use the transaction code: ABAR to run consistency checks on asset accounting data. This can help identify any issues that need to be resolved.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant transaction logs.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  OB29: Define fiscal year variant.
  OB52: Open and close posting periods.
  AS03: Display asset master data.
  ABAR: Run asset accounting consistency checks.
  
  
  
  Documentation: Refer to SAP Help documentation for Asset Accounting for detailed information on fiscal year settings and asset management processes.
  
  
  By following these steps, you should be able to identify and resolve the issue causing the AA652 error in SAP.