Do you have any question about this error?
Message type: E = Error
Message class: AU - FI-AA utility program error messages
Message number: 273
Message text: Balance carryforward not possible due to different open fiscal years
You want to execute the balance carryforward to &V3& for company code
&V1& and ledger &V2&. This affects several depreciation areas in Asset
Accounting. Fiscal year &V3& is open in one of the depreciation areas,
but it is closed in one of the other depreciation areas. The balance
carryforward cannot be performed because of this.
The balance carryforward to &V3& was not executed for company code &V1&
and ledger &V2&.
If the balance carryforward is relevant for Asset Accounting, then
reopen fiscal year &V3& in Asset Accounting for all the affected
depreciation areas.
If the balance carryforward is irrelevant for Asset Accounting, then
close fiscal year &V3& in Asset Accounting.
Then perform the balance carryforward again.
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.
AU273
- Balance carryforward not possible due to different open fiscal years ?The SAP error message AU273, which states "Balance carryforward not possible due to different open fiscal years," typically occurs during the year-end closing process when attempting to carry forward balances from one fiscal year to the next. This error indicates that there are discrepancies in the fiscal year settings between the periods you are trying to carry forward.
Cause:
- Different Open Fiscal Years: The error usually arises when the fiscal year settings for the company code or controlling area are not aligned. For example, if one fiscal year is open in one area but closed in another, the system will not allow the carryforward.
- Incorrect Configuration: The configuration of fiscal year variants may not be consistent across different modules or areas (e.g., Financial Accounting (FI) and Controlling (CO)).
- Unfinished Closing Activities: If there are pending closing activities in the previous fiscal year, it can prevent the carryforward process.
Solution:
Check Open Fiscal Years:
- Go to the transaction code OB52 (Change View "Open and Close Posting Periods") and verify the open and closed periods for the relevant company code and controlling area.
- Ensure that the fiscal year you are trying to carry forward is open in all relevant areas.
Align Fiscal Year Variants:
- Check the fiscal year variant settings in OB29 (Maintain Fiscal Year Variants) to ensure that they are consistent across all relevant modules.
- Make sure that the fiscal year variant assigned to the company code is the same as that assigned to the controlling area.
Complete Year-End Closing Activities:
- Ensure that all necessary year-end closing activities for the previous fiscal year are completed. This includes posting all necessary adjustments and ensuring that all accounts are reconciled.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific steps related to your organization's configuration.
Run Balance Carryforward Again:
- After addressing the issues, attempt to run the balance carryforward process again using transaction code S_ALR_87012357 or AJAB (Carry Forward Balances).
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to fiscal year carryforward.
User Roles: Ensure that you have the necessary authorizations to make changes to fiscal year settings and to perform carryforward operations.
By following these steps, you should be able to resolve the AU273 error and successfully carry forward balances to the new fiscal year.
Get instant SAP help. Start your 7-day free trial now.
AU272
CCode &1: Fiscal year change &2 performed, postprocessing necessary
What causes this issue? The fiscal year change to fiscal year &V2& in company code &V1& was finished <ZH>successfully</>....
AU271
CCode &1: Fiscal year change &2 has failed for some fixed assets
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
AU301
Client of input file & is not the same as the logon client &
What causes this issue? The client (&V1&) of the sequential input file is not the same as the logon client (&V2&).System Response Th...
AU390
Values for &3 have changed in dep. area &1 in fiscal year &2
What causes this issue? Depreciation terms were changed in depreciation area &v1& since the last time depreciation was recalculated. The valu...
Click on this link to search all SAP messages.