Do you have any question about this error?
Message type: E = Error
Message class: FAA_CMP - Asset Accounting: Configuration Object Company Code
Message number: 060
Message text: Legacy data transfer date &1 is invalid for company code &2
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
FAA_CMP060
- Legacy data transfer date &1 is invalid for company code &2 ?The SAP error message FAA_CMP060 indicates that there is an issue with the legacy data transfer date for a specific company code. This error typically arises during the migration of legacy data into the SAP system, particularly in the context of Asset Accounting (FI-AA).
Cause:
The error message FAA_CMP060 is triggered when:
- The legacy data transfer date specified is not valid for the given company code.
- The date may fall outside the permissible range for asset transactions in the company code.
- The fiscal year or period for the specified date may not be open or may have been closed in the system.
- There may be inconsistencies in the configuration of the company code or the asset accounting settings.
Solution:
To resolve the FAA_CMP060 error, you can take the following steps:
Check the Legacy Data Transfer Date:
- Ensure that the date you are using for the legacy data transfer is correct and falls within the valid range for the company code.
Verify Company Code Settings:
- Go to the configuration settings for the company code in SAP and check the fiscal year variant and the periods that are open for posting.
- Ensure that the fiscal year and periods are correctly set up and that the date you are using is within an open period.
Adjust the Date:
- If the date is outside the valid range, adjust it to a valid date that is within the open periods for the company code.
Check Asset Accounting Configuration:
- Review the configuration settings for Asset Accounting (FI-AA) to ensure that they are correctly set up for the company code in question.
Consult Documentation:
- Refer to SAP documentation or help resources for additional guidance on legacy data transfer and the specific requirements for your version of SAP.
Testing:
- After making the necessary adjustments, perform a test transfer to see if the error persists.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the FAA_CMP060 error message in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
FAA_CMP059
LDT date &1 is in the future but BCF was not executed and postings exist
What causes this issue? While setting up the company code for Asset Accounting<(>,<)> you want to change the current fiscal year for a le...
FAA_CMP058
Runtime settings of company code &1 are inconsistent
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAA_CMP061
Legacy data transfer date &1 must not be before G/L migration date &2
What causes this issue? The legacy data transfer date &V1& is before the G/L migration date &V2& . This is <ZH>not </>all...
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...
Click on this link to search all SAP messages.