How To Fix CNV_20100347 - Participating chart of accounts & has no company codes


SAP Error Message - Details

  • Message type: E = Error

  • Message class: CNV_20100 - Messageclass for chart of account conversion

  • Message number: 347

  • Message text: Participating chart of accounts & has no company codes

  • Show details Hide details
  • What causes this issue?

    Participating chart of accounts &V1& is no group chart of accounts, and
    no company code uses it as operative or country-specific chart of
    accounts.

    System Response

    Information
    Chart of accounts &V1& will be loaded into the list of relevant
    organizational units to be used during derivation and delimitation.

    How to fix this error?

    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_20100347 - Participating chart of accounts & has no company codes ?

    The SAP error message CNV_20100347 indicates that a participating chart of accounts does not have any associated company codes. This error typically arises during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools for data transfer.

    Cause:

    1. Missing Company Codes: The chart of accounts you are trying to use is not linked to any company codes in the system. This can happen if the chart of accounts was created but not assigned to any company codes.
    2. Incorrect Configuration: There may be a configuration issue where the chart of accounts is not properly set up in the system.
    3. Data Migration Issues: During the migration process, the mapping of charts of accounts to company codes may not have been done correctly.

    Solution:

    1. Check Chart of Accounts Configuration:

      • Go to the SAP transaction code OBY6 (or use the relevant configuration path) to check the configuration of the chart of accounts.
      • Ensure that the chart of accounts in question is assigned to the relevant company codes.
    2. Assign Company Codes:

      • If the chart of accounts is not assigned to any company codes, you need to assign it. This can be done in the same configuration area (OBY6).
      • Make sure to save your changes after assigning the company codes.
    3. Review Migration Settings:

      • If you are using a migration tool, review the mapping settings to ensure that the chart of accounts is correctly linked to the intended company codes.
      • Check the migration logs for any additional errors or warnings that may provide more context.
    4. Consult Documentation:

      • Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific steps or considerations for your version of SAP.
    5. Testing:

      • After making the necessary changes, perform a test run of the migration process to ensure that the error does not reoccur.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (for chart of accounts assignment) and OBD2 (for company code settings).
    • SAP Notes: Check for any SAP Notes related to this error message for additional troubleshooting steps or patches.
    • Migration Cockpit: If using the SAP S/4HANA Migration Cockpit, ensure that you are following the correct procedures for data migration and that all prerequisites are met.

    By following these steps, you should be able to resolve the error CNV_20100347 and successfully link your chart of accounts to the appropriate 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