Do you have any question about this error?
Message type: E = Error
Message class: AY - Deprec. simulation - maint. module (AIPS) /gen. master data
Message number: 159
Message text: Information about last completed fiscal year is incomplete
For valuation area &V2&, company code &V1& still does <ZH>not</> contain
information about the last closed fiscal year.
Processing terminates.
Check the last closed fiscal year for the valuation area. To do so, open
the <LS>Make Company Code Settings</> app.
Check the last closed fiscal year for the valuation area. You can check
this in Customizing for <LS>Asset Accounting</> under
<DS:SIMG.FAA_CMP_DC>Make Settings for Company Code</> (transaction <AB>
FAA_CMP</>).
If the last closed fiscal year is initial, the current error message is
rightly issued.
To resolve the problem, check whether the <LS>Legacy Data Transfer</>
tab contains at least one segment for the legacy data transfer.
If this is <ZH>not</> the case, create a segment with a legacy data
transfer date.
The system then automatically sets the information for the current and
closed fiscal years.
If there is exactly one segment that is <ZH>not</> yet closed, try to
update the segment by making a change and saving the data.
If it is <ZH>not</> possible to set a closed fiscal year for the
valuation area, contact SAP.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
AY159
- Information about last completed fiscal year is incomplete ?The SAP error message AY159, which states "Information about last completed fiscal year is incomplete," typically occurs when there are missing or incomplete settings related to the fiscal year in the system. This can affect various financial processes, including closing periods, reporting, and other financial transactions.
Cause:
- Incomplete Fiscal Year Settings: The fiscal year settings in the system may not be fully configured. This includes missing entries for periods, or the fiscal year variant may not be properly assigned.
- Missing Data: There may be missing data in the financial documents or master data that is required for the fiscal year.
- Open Periods: The system may have open periods that are not properly closed, leading to inconsistencies in the fiscal year data.
- Configuration Issues: There may be issues with the configuration of the controlling area or company code that affect the fiscal year settings.
Solution:
Check Fiscal Year Variant:
- Go to the transaction code OB29 to check the fiscal year variant settings.
- Ensure that the fiscal year variant is correctly assigned to the company code and that all periods are defined.
Complete Missing Data:
- Review the financial documents and master data to ensure that all necessary information for the last completed fiscal year is present.
- If any data is missing, complete it as required.
Close Open Periods:
- Check if there are any open periods that need to be closed. You can do this in transaction code OB52.
- Ensure that the periods for the last completed fiscal year are closed.
Run Year-End Closing Programs:
- Execute the year-end closing programs to ensure that all necessary processes for closing the fiscal year have been completed.
Consult Documentation:
- Review SAP documentation or help files related to fiscal year closing and configuration for additional guidance.
Check for Notes and Patches:
- Sometimes, SAP releases notes or patches that address specific issues. Check the SAP Support Portal for any relevant notes related to this error.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP Financial Accounting.
Get instant SAP help. Start your 7-day free trial now.
AY158
Deletion flag was removed.
What causes this issue? The indicator "marked for deletion" was set for the asset.System Response This indicator is no longer used, starti...
AY157
Customizing inconsistency - business area was set as ready for input
What causes this issue? Business area balance sheets are to be created in company code &V1&. For this reason, every asset has to be uniquely ...
AY160
No depreciation area in company code & allows group assets.
What causes this issue? You cannot create group assets in company code &v1&. There are no depreciation areas that can manage group assets in ...
AY161
Deleting is not possible. The asset already has values.
What causes this issue? Asset &v1& sub-number &v2& already has values.System Response Asset &v1& - &v2& cannot be de...
Click on this link to search all SAP messages.