How To Fix APERB226 - Indicator for differing fiscal year variants not set in CoCd &1

SAP Error Message - Details

• Message type: E = Error

• Message class: APERB - Error Messages for Periodic Posting Run

• Message number: 226

• Message text: Indicator for differing fiscal year variants not set in CoCd &1

What causes this issue?

You want to enter a ledger group on the selection screen.
However, in Customizing for <LS>Asset Accounting</> the <DS:DE.XDFYV>
Alternative Fiscal Year Variants</> indicator is <ZH>not</> set for
company code &V1&.

System Response

Depreciation specific to ledger groups is <ZH>not</> possible in company
code &V1&.

How to fix this error?

In that case, you do <ZH>not</> need to enter a ledger group.
If you want to post depreciation only for a certain ledger group,
contact your system administrator.

Procedure for System Administrators

In company code &V1&, check if the prerequisites are met for activating
posting of depreciation per ledger group:
Activating the function in company code &V1& only makes sense if
different fiscal year variants are used in different ledgers.
<ZH>No</> further restarts of depreciation runs can be required.
If you activate this function during the fiscal year, it can result in
inconsistent depreciation values. We recommend activating this function
at the fiscal year change.
To activate this function, in Customizing for <LS>Asset Accounting</>
under <DS:SIMG.FIAA_BEW_GJAHR_NEWGL_DC>Allow Differing Variants for
Depreciation Areas with G/L Integration</>, set the <LS>Alternative
Fiscal Year Variants</> indicator.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message APERB226 - Indicator for differing fiscal year variants not set in CoCd &1 ?

  The SAP error message APERB226 indicates that there is a mismatch in the fiscal year variants between the company code (CoCd) and the controlling area. This error typically arises when you are trying to perform a transaction that requires consistency between the fiscal year settings in the controlling area and the company code.
  Cause:
  
  Different Fiscal Year Variants: The company code and the controlling area have different fiscal year variants. For example, if the company code is set to a calendar year fiscal year variant (e.g., January to December) and the controlling area is set to a non-calendar year fiscal year variant, this inconsistency will trigger the error.
  Configuration Issues: The fiscal year variant settings may not have been properly configured during the setup of the company code or controlling area.
  
  Solution:
  
  
  Check Fiscal Year Variants:
  
  Go to the SAP transaction code OB29 to check the fiscal year variant settings for the company code.
  Go to the transaction code OKKP to check the fiscal year variant settings for the controlling area.
  Ensure that both the company code and the controlling area are using the same fiscal year variant.
  
  
  
  Adjust Settings:
  
  If they are different, you will need to either change the fiscal year variant of the company code or the controlling area to ensure they match.
  If you need to change the fiscal year variant, you may need to consult with your SAP administrator or a functional consultant, as changing these settings can have significant implications on financial reporting and data integrity.
  
  
  
  Reassign Controlling Area:
  
  If necessary, you can reassign the controlling area to the company code with the correct fiscal year variant. This can be done in the configuration settings.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB29: Maintain Fiscal Year Variants
  OKKP: Maintain Controlling Area
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on configuring fiscal year variants and controlling areas.
  Consulting: If you are unsure about making changes, it is advisable to consult with an SAP FI/CO consultant who can provide guidance based on your specific system configuration and business requirements.
  
  By ensuring that the fiscal year variants are consistent between the company code and the controlling area, you should be able to resolve the APERB226 error.