How To Fix CNV_20200_CHECK168 - Participating company codes with and without fiscal year variant

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20200_CHECK - Messages for check functions (company code merge)

• Message number: 168

• Message text: Participating company codes with and without fiscal year variant

What causes this issue?

The are participating company codes with and without fiscal year
variant.
Reference company code &V1& has fiscal year variant &V2&.
This fiscal year variant will take priority in the company code settings
by default.

System Response

Error

How to fix this error?

There is at least one company code without a fiscal year variant. Check
your Customizing settings for the fiscal year variant, specify a fiscal
year variant and run the check again.

Procedure for System Administrators

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 CNV_20200_CHECK168 - Participating company codes with and without fiscal year variant ?

  The SAP error message CNV_20200_CHECK168 typically arises during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there are inconsistencies between participating company codes in terms of their fiscal year variants.
  Cause:
  The error occurs when there are company codes that have different fiscal year variants. In SAP, a fiscal year variant defines the financial year and the periods within it. If you are trying to migrate or consolidate data from multiple company codes, all participating company codes must have the same fiscal year variant to ensure consistency in financial reporting and data integrity.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify Company Codes: Determine which company codes are involved in the migration and check their fiscal year variants. You can do this by navigating to the configuration settings in SAP:
  
  Use transaction code OB29 to view the fiscal year variants assigned to each company code.
  
  
  
  Standardize Fiscal Year Variants: 
  
  If you find that some company codes have different fiscal year variants, you will need to standardize them. This can involve changing the fiscal year variant of one or more company codes to match the others.
  Be cautious when changing fiscal year variants, as this can have implications for financial reporting and historical data.
  
  
  
  Adjust Migration Settings: If changing the fiscal year variants is not feasible, you may need to adjust your migration settings or approach. This could involve migrating data in separate batches based on fiscal year variants.
  
  
  Consult Documentation: Review SAP documentation or notes related to the migration process for any specific guidelines or best practices regarding fiscal year variants.
  
  
  Testing: After making changes, perform a test migration to ensure that the error is resolved and that data integrity is maintained.
  
  
  Related Information:
  
  Fiscal Year Variant: A fiscal year variant in SAP defines how the fiscal year is structured, including the number of periods and special periods.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB29 (to view fiscal year variants) and OB37 (to assign fiscal year variants to company codes).
  SAP Notes: Check for any SAP Notes related to the CNV_20200_CHECK168 error for additional insights or updates from SAP.
  
  If you continue to experience issues after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.