How To Fix ACC_AA100 - Fiscal year variants in company code &1 have differing end dates

SAP Error Message - Details

• Message type: E = Error

• Message class: ACC_AA - Message Class for Function Group ACC_AA

• Message number: 100

• Message text: Fiscal year variants in company code &1 have differing end dates

What causes this issue?

Accounting principle &V2& and accounting principle &V3& are assigned to
at least one depreciation area in chart of depreciation &V4&.
The last day of the fiscal year variant of the representative ledger of
ledger group &V2& in company code &V1& differs from the last day of the
fiscal year variant of the representative ledger of ledger group &V3&.
However, both fiscal year variants must have the same start and end
date. Only the periods within the fiscal year can be different in the
two variants.

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?

Assign accounting principles that have fiscal year variants with the
same start and end date to the depreciation areas.

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 ACC_AA100 - Fiscal year variants in company code &1 have differing end dates ?

  The SAP error message ACC_AA100 indicates that there is a mismatch in the fiscal year variants for the specified company code. This typically occurs when the fiscal year variants assigned to different company codes have different end dates, which can lead to inconsistencies in financial reporting and asset accounting.
  Cause:
  
  Different Fiscal Year Variants: The company code in question has been assigned a fiscal year variant that has a different end date compared to another company code.
  Configuration Issues: This can happen if the fiscal year variants were not set up correctly during the configuration of the system or if changes were made to one company code without corresponding changes to others.
  Data Migration Issues: If data was migrated from another system, discrepancies in fiscal year variants may have been introduced.
  
  Solution:
  
  
  Check Fiscal Year Variants:
  
  Go to the transaction code OB29 (Define Fiscal Year Variants) in SAP.
  Review the fiscal year variants assigned to the company codes involved. Ensure that they have the same end dates.
  
  
  
  Align Fiscal Year Variants:
  
  If you find discrepancies, you may need to either change the fiscal year variant of one of the company codes or create a new fiscal year variant that aligns with the others.
  Ensure that all company codes that need to report together have the same fiscal year variant.
  
  
  
  Adjust Configuration:
  
  If necessary, adjust the configuration in the system to ensure that all relevant company codes are using the same fiscal year variant.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP Basis or Finance team to ensure that any changes made are compliant with your organization's financial reporting requirements.
  
  
  
  Testing:
  
  After making changes, perform testing to ensure that the error is resolved and that financial reporting is functioning correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB29: Define Fiscal Year Variants
  OBA7: Assign Fiscal Year Variant to Company Code
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to this error.
  Documentation: Review SAP Help documentation for Asset Accounting and Fiscal Year Variants for more detailed information on configuration and best practices.
  
  By following these steps, you should be able to resolve the ACC_AA100 error and ensure that your fiscal year variants are correctly aligned across company codes.