Do you have any question about this error?
Message type: E = Error
Message class: FAA_CMP - Asset Accounting: Configuration Object Company Code
Message number: 059
Message text: LDT date &1 is in the future but BCF was not executed and postings exist
While setting up the company code for Asset Accounting<(>,<)> you want
to change the current fiscal year for a ledger.
Relating to the current fiscal year, the legacy data transfer date can
be one year in the future, but only if one of the following
prerequisites is fulfilled:
The balance carryforward has already been executed for this year.
No postings exist in the current fiscal year.
However, in the present case, the legacy data transfer date &V1& is in
the future, but the balance carryforward has <ZH>not</> been executed
and postings exist.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please specify a valid date.
Error message extract from SAP system. Copyright SAP SE.
FAA_CMP059
- LDT date &1 is in the future but BCF was not executed and postings exist ?The SAP error message FAA_CMP059 indicates that there is a discrepancy related to the Last Depreciation (LDT) date in the Asset Accounting module. Specifically, it means that the LDT date is set in the future, but the system has not executed the Balance Carryforward (BCF) process, and there are existing postings for the asset.
Cause:
- Future LDT Date: The LDT date is set to a future date, which is not allowed if there are existing postings for the asset.
- BCF Not Executed: The Balance Carryforward process has not been executed for the asset, which is necessary to ensure that the asset's depreciation is correctly carried forward into the new fiscal year.
- Postings Exist: There are postings (e.g., acquisitions, retirements, or adjustments) that have been made to the asset after the LDT date, which complicates the situation.
Solution:
To resolve this error, you can follow these steps:
Check the LDT Date:
- Review the asset master data to confirm the LDT date. If it is set in the future, you may need to adjust it to a valid date that is not in the future.
Execute Balance Carryforward (BCF):
- If the LDT date is correct, ensure that the Balance Carryforward process has been executed for the relevant fiscal year. This can typically be done through the transaction code AFBC (Balance Carryforward).
Review Postings:
- Check for any postings that exist for the asset after the LDT date. If there are postings, you may need to adjust or reverse them as necessary.
Consult Documentation:
- Refer to SAP documentation or your organization's internal guidelines for handling asset accounting issues, as there may be specific procedures to follow.
Contact Support:
- If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Related Information:
By following these steps, you should be able to resolve the FAA_CMP059 error and ensure that your asset accounting is accurate and compliant with SAP requirements.
Get instant SAP help. Start your 7-day free trial now.
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_CMP057
Ledger &2, depreciation area &1: Closed fiscal year is invalid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAA_CMP060
Legacy data transfer date &1 is invalid for company code &2
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...
Click on this link to search all SAP messages.