Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 935
Message text: Legacy data transfer date &3 inconsistent w/ last closed fiscal year &2
The legacy data transfer date and the last closed fiscal year do not go
together. The earliest possible date for the legacy data transfer is the
last day of the last closed fiscal year.
Example for the correct specification:
Legacy data transfer 12.31 current year -> last closed fiscal year:
Current year
Legacy data transfer 06.30 following year -> last closed fiscal year:
Current Year
Correct the date of the legacy data transfer &V3&.
This is not required if you simply want to display the legacy asset
data.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message AA935 indicates that there is an inconsistency between the legacy data transfer date and the last closed fiscal year in the Asset Accounting (FI-AA) module. This error typically arises when you are trying to transfer legacy asset data into the SAP system, and the date you are using for the transfer does not align with the fiscal year that has been closed in the system.
Cause:
- Inconsistent Dates: The legacy data transfer date you are trying to use is earlier than the last closed fiscal year. For example, if the last closed fiscal year is 2022, and you are trying to transfer data with a date in 2021 or earlier, this error will occur.
- Fiscal Year Settings: The fiscal year settings in the system may not be configured correctly, or the fiscal year may not be closed properly.
- Data Entry Error: There may be a mistake in the date entered during the legacy data transfer process.
Solution:
- Check the Transfer Date: Ensure that the legacy data transfer date is within the range of open fiscal years. You can do this by checking the fiscal year settings in the SAP system.
- Adjust the Transfer Date: If the transfer date is incorrect, adjust it to a date that is within the open fiscal year.
- Review Fiscal Year Closing: Verify that the fiscal year has been closed correctly. If necessary, consult with your finance team to ensure that the fiscal year closing process has been completed properly.
- Use Transaction Code OAAQ: You can use transaction code OAAQ to check the status of the fiscal years and make any necessary adjustments.
- Consult Documentation: Refer to SAP documentation or help resources for more detailed guidance on handling legacy data transfers and fiscal year settings.
Related Information:
By following these steps, you should be able to resolve the AA935 error and successfully complete your legacy data transfer in SAP.
Sign up takes 1 minute. 7-day free trial.
AA934 Maintain scrap value in foreign currency in dep.area &
What causes this issue? Depreciation area &V1& adopts identical values ...
AA933 Contact your Systems Specialist
What causes this issue? No files have been defined for company code &V1&...
AA936 In index series &, the index class & is missing
What causes this issue? Index series &V1& has the classification &V...
AA937 Index series & has several base years (Enter another index series)
What causes this issue? Index series &V1& belongs to an index class tha...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.