Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: APERB - Error Messages for Periodic Posting Run
Message number: 221
Message text: Non-calendar fiscal years in company code &1
In company code &V1&, the representative ledgers of ledger groups &V2&
and &V3& use fiscal year variants, in which the fiscal year begins or
ends on different days.
Activating the <LS>Alternative Fiscal Year Variants</> function is <ZH>
not</> possible for non-calendar fiscal years.
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.
APERB221
- Non-calendar fiscal years in company code &1 ?The SAP error message APERB221 indicates that there is a mismatch between the fiscal year variant assigned to a company code and the fiscal year settings in the system. Specifically, it occurs when a non-calendar fiscal year is being used, but the system is expecting a calendar year.
Cause:
- Fiscal Year Variant Configuration: The company code is assigned a fiscal year variant that does not match the calendar year. For example, if the fiscal year variant is set to a non-calendar year (like April to March), but the system is trying to process transactions as if it were a calendar year (January to December), this error can occur.
- Transaction Date: The date of the transaction being processed may fall outside the defined periods of the fiscal year variant assigned to the company code.
- Incorrect Settings: There may be incorrect settings in the configuration of the fiscal year variant or the company code.
Solution:
Check Fiscal Year Variant:
- Go to the configuration settings in SAP (Transaction code: SPRO).
- Navigate to Financial Accounting (New) > Financial Accounting Global Settings (New) > Fiscal Year > Define Fiscal Year Variants.
- Verify that the fiscal year variant assigned to the company code is correct and matches the intended fiscal year structure.
Review Company Code Settings:
- Check the company code settings (Transaction code: OX02).
- Ensure that the fiscal year variant assigned to the company code is appropriate for the transactions being processed.
Adjust Transaction Dates:
- If the transaction date is outside the allowed periods, adjust the date to fall within the valid range of the fiscal year variant.
Consult Documentation:
- Review SAP documentation or consult with your SAP Basis or Finance team to ensure that the fiscal year settings are correctly configured.
Testing:
- After making changes, test the transaction again to ensure that the error is resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with SAP support or a consultant who specializes in SAP Financials for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
APERB220
No posting depreciation area could be determined
What causes this issue? You have started a report for depreciation area &V2& in company code &V1&, for which depreciation terms have ...
APERB219
Report during year for posted deprec. from derived area &1 not possible
What causes this issue? For company code &V2&, more than two fiscal year variants were maintained for the depreciation areas. For a report da...
APERB222
Differing fiscal year variant in ledger group &2
What causes this issue? The entered depreciation area is assigned to ledger group &V2&; this ledger group uses fiscal year variant &V3&am...
APERB223
In CoCd &1 base and revaluation area have different ledger groups
What causes this issue? In company code &V1&, the accounting principle &V2& was determined from the base depreciation area, but accou...
Click on this link to search all SAP messages.