Message type: E = Error
Message class: AU - FI-AA utility program error messages
Message number: 172
Message text: Report date is in a closed fiscal year
The report date is in the past.
Here the report date is allowed to be the end of the year as well as any
period end during the fiscal year.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
In an asset report during the fiscal year (report date for a period end
within the year) in a closed fiscal year, it can be the case that the
results for depreciation or the net book value are different between the
historical calculation and the current calculation for the report date.
The reason for this is if there were any changes to asset-related
depreciation terms, such as the depreciation key, useful life, and so
on. In the case of such changes, the asset values are recalculated with
the currently entered depreciation terms.
Error message extract from SAP system. Copyright SAP SE.
AU172
- Report date is in a closed fiscal year ?The SAP error message AU172, which states "Report date is in a closed fiscal year," typically occurs when you attempt to run a report or transaction that involves a date falling within a fiscal year that has already been closed. This is a common issue in financial reporting and accounting processes within SAP.
Cause: Closed Fiscal Year: The fiscal year you are trying to report on has been closed in the system, meaning that no further postings or changes can be made for that year. Incorrect Date Selection: The date you selected for the report may inadvertently fall within a closed fiscal year. Configuration Settings: The system settings may restrict reporting on closed fiscal years to maintain data integrity and compliance.
Solution: Change the Report Date: Adjust the date in your report to fall within an open fiscal year. This is the simplest solution if you do not need to report on the closed year. Open the
Get instant SAP help. Sign up for our Free Essentials Plan.
AU171
RAALTD11 cannot be started in a Unicode system
What causes this issue? You tried to start RAALTD11_NONUNICODE in a Unicode system. However, the RAALTD11_NONUNICODE report is not Unicode-capable.Sy...
AU170
XPRA Report RAIXPR05 - update of &1 records completed successfully
What causes this issue? &1 appropriation requests, for which there is no ID that uses a coding mask, were found in the database. For these record...
AU173
Account '&2' could not be determined for area &3
What causes this issue? The system could <ZH>not</> find account '&V2&' for company code &V1& and depreciation ...
AU174
Acct "Offsetting acct for legacy data transfer" in CoCd &1 not maintained
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.