Do you have any question about this error?
Message type: E = Error
Message class: FAA_CMP - Asset Accounting: Configuration Object Company Code
Message number: 064
Message text: LDT date changed; check if the fiscal year has to be adjusted
The current legacy data transfer segment has the status 'In
Preparation'; <ZH>no</> assets have been created for this legacy data
transfer segment, yet.
In such a case, it is still possible to change the legacy data transfer
date. It is also possible to change the current fiscal year or the
closed fiscal year.
Note:
When you create the first legacy data transfer segment, the system
automatically derives the current fiscal year and the closed fiscal year
on ledger and depreciation area level.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you want to change the current fiscal year or the closed fiscal year
at a later date, you do this as follows:
You can change it in the ledger settings, provided that <ZH>no</> asset
accounting postings exist in the current company code.
Or you change it by using the functions for closing or reopening fiscal
years.
Error message extract from SAP system. Copyright SAP SE.
FAA_CMP064
- LDT date changed; check if the fiscal year has to be adjusted ?The SAP error message FAA_CMP064 indicates that there is an issue with the LDT (Last Depreciation Time) date in the Asset Accounting module. This error typically arises when there is a discrepancy between the LDT date and the fiscal year settings in the system. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
- LDT Date Change: The LDT date for an asset has been changed, which may not align with the fiscal year settings in the system.
- Fiscal Year Settings: The fiscal year may not be properly configured, or the asset may be set to a fiscal year that does not match the LDT date.
- Depreciation Run: If a depreciation run has been executed, and the LDT date is altered afterward, it can lead to inconsistencies.
- Asset Master Data Changes: Changes made to the asset master data, such as the acquisition date or useful life, can also trigger this error.
Solution:
- Check LDT Date: Verify the LDT date for the asset in question. Ensure that it is set correctly and corresponds to the fiscal year.
- Review Fiscal Year Settings: Check the fiscal year settings in the system. Ensure that the fiscal year is correctly defined and that it aligns with the LDT date.
- Adjust Fiscal Year: If necessary, adjust the fiscal year settings to accommodate the LDT date. This may involve changing the fiscal year variant or adjusting the periods.
- Re-run Depreciation: If changes are made to the LDT date or fiscal year settings, re-run the depreciation calculation to ensure that all values are updated correctly.
- Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific steps related to your version of SAP.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with SAP support or a consultant who specializes in Asset Accounting for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FAA_CMP063
Fiscal years could not be derived from LDT date for ledger &1
What causes this issue? When you create the first legacy data transfer segment, the system automatically derives the current fiscal year and the clos...
FAA_CMP062
Not all previous legacy data transfer segments have status 'completed'
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAA_CMP065
LDT date must be later than the LDT dates of previous LDT segments
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAA_CMP066
Only possible to deactivate company code if there are no active assets
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.