How To Fix APERB213 - 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: 213

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

What causes this issue?

You have entered a ledger group on the selection screen.
However, in Customizing for <LS>Asset Accounting</> the <LS>Alternative
Fiscal Year Variants</> indicator is <ZH>not</> set for company code
&V1&. Therefore, entering a ledger group does <ZH>not</> serve any
purpose, unless you want to display a depreciation run that was executed
while the <LS>Alternative Fiscal Year Variants</> function was active.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Do <ZH>not</> enter a ledger group, or ignore the warning by choosing
<LS>Continue</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message APERB213 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 these two entities, such as during the posting of financial documents or during the execution of certain reports.
  Cause:
  The error occurs when:
  
  The fiscal year variant assigned to the company code does not match the fiscal year variant assigned to the controlling area.
  The system requires that both the company code and the controlling area have the same fiscal year variant to ensure proper financial reporting and controlling.
  
  Solution:
  To resolve the APERB213 error, you need to ensure that the fiscal year variants for the company code and the controlling area are aligned. Here are the steps to do this:
  
  
  Check the Fiscal Year Variant for the Company Code:
  
  Go to the transaction code OBY6 (or navigate through the menu: SPRO > Financial Accounting > General Ledger > Master Data > G/L Account > Prepare for Migration > Define Company Code).
  Find the company code in question and check its assigned fiscal year variant.
  
  
  
  Check the Fiscal Year Variant for the Controlling Area:
  
  Go to the transaction code OKKP (or navigate through the menu: SPRO > Controlling > General Controlling > Master Data > Controlling Area > Define Controlling Area).
  Find the controlling area and check its assigned fiscal year variant.
  
  
  
  Align the Fiscal Year Variants:
  
  If the fiscal year variants are different, you will need to either change the fiscal year variant of the company code or the controlling area to ensure they match.
  Note that changing the fiscal year variant can have implications on financial reporting, so it should be done with caution and ideally during a period of low activity.
  
  
  
  Test the Changes:
  
  After making the necessary changes, perform the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Fiscal Year Variants: These define the structure of the fiscal year, including the number of posting periods and special periods. They are crucial for financial reporting and must be consistent across related entities.
  Transaction Codes:
  
  OBY6: To check and maintain company code settings.
  OKKP: To check and maintain controlling area settings.
  
  
  Documentation: Always refer to SAP documentation or consult with your SAP Basis or Finance team for guidance on making changes to configuration settings.
  
  By ensuring that the fiscal year variants are consistent, you should be able to resolve the APERB213 error and proceed with your transactions without further issues.