How To Fix AA653 - SYST: Error when calculating last day in fiscal period --> F1

SAP Error Message - Details

• Message type: E = Error

• Message class: AA - Messages for Asset Accounting

• Message number: 653

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

What causes this issue?

An error occurred when determining the last day of the fiscal period
&V2& &V1& in period version &V3&.

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?

There are three things which could lead to this error:
The period version &V3& allocated to the company code, has not been
created. In this case, you should create the period version.
The period version has been created, however the allocation of calendar
dates to the fiscal periods has not been correctly performed, or in
particular with calendar-dependent period versions has not been
completely performed.
The fiscal period &V2& &V1& is invalid. This is a system error. Please
contact your Systems Specialist.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message AA653 indicates that there is an issue with calculating the last day of a fiscal period in the Asset Accounting (AA) module. This error typically arises when there is a problem with the configuration of the fiscal year variant or the period settings in the system.
  
  Cause:
  
  Fiscal Year Variant Configuration: The fiscal year variant may not be set up correctly, or there may be inconsistencies in the fiscal year settings.
  Period Locking: The period may be locked for posting, which prevents the system from calculating the last day of the fiscal period.
  Missing or Incorrect Period Settings: There may be missing or incorrect settings for the fiscal periods in the configuration.
  Date Issues: The system may be trying to calculate a date that does not exist, such as a leap year issue or an incorrect date format.
  
  
  Solution:
  
  
  Check Fiscal Year Variant:
  
  Go to the configuration settings for the fiscal year variant (Transaction