How To Fix CNV_20200_CHECK152 - Particip. company codes use different FY variants for asset accounting


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 152

  • Message text: Particip. company codes use different FY variants for asset accounting

  • Show details Hide details
  • You cannot run the transformation solution Company Code Merge because
    certain prerequisites have not been met. We recommend that you contact
    SAP for support by creating a ticket using component CA-LT-CNV.

    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_CHECK152 - Particip. company codes use different FY variants for asset accounting ?

    The SAP error message CNV_20200_CHECK152 indicates that there is a mismatch in the fiscal year (FY) variants used for asset accounting between participating company codes during a data migration or conversion process. This error typically arises in scenarios such as system migrations, consolidations, or when integrating multiple company codes that have different fiscal year settings.

    Cause:

    The primary cause of this error is that the participating company codes have been configured with different fiscal year variants in the Asset Accounting (FI-AA) module. Each fiscal year variant defines the structure of the fiscal year, including the number of posting periods, special periods, and the start and end dates of the fiscal year. When these variants differ across company codes, it can lead to inconsistencies in financial reporting and asset management.

    Solution:

    To resolve this error, you need to ensure that all participating company codes use the same fiscal year variant for asset accounting. Here are the steps to address the issue:

    1. Identify Company Codes: Determine which company codes are involved in the error message.

    2. Check Fiscal Year Variants:

      • Go to the transaction code OB29 (or navigate through the menu: SPRO > Financial Accounting > Financial Accounting Global Settings > Fiscal Year > Maintain Fiscal Year Variants).
      • Review the fiscal year variants assigned to each company code.
    3. Align Fiscal Year Variants:

      • If the company codes are using different fiscal year variants, you will need to either:
        • Change the fiscal year variant of one or more company codes to match the others.
        • Create a new fiscal year variant that can be applied uniformly across the relevant company codes.
    4. Adjust Configuration:

      • If you decide to change the fiscal year variant, ensure that you adjust any related configurations and settings that may be impacted by this change.
    5. Test the Changes: After making the necessary adjustments, perform tests to ensure that the error is resolved and that the asset accounting functions correctly across the company codes.

    6. Re-run the Migration/Conversion: Once the fiscal year variants are aligned, re-run the migration or conversion process that triggered the error.

    Related Information:

    • Fiscal Year Variant: A fiscal year variant defines the structure of the fiscal year for financial reporting. It includes the number of periods, special periods, and the start and end dates.
    • Asset Accounting (FI-AA): This module in SAP is responsible for managing fixed assets, including acquisition, depreciation, and disposal.
    • Data Migration: When migrating data between systems or consolidating company codes, it is crucial to ensure that configurations such as fiscal year variants are consistent to avoid errors.

    By following these steps, you should be able to resolve the CNV_20200_CHECK152 error and ensure that your asset accounting processes function smoothly across the participating company codes.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant