Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix CNV_20100223 - Obsolete entry at B level for G/L account &1 &2 in CoCd &3


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 223

  • Message text: Obsolete entry at B level for G/L account &1 &2 in CoCd &3

  • Show details Hide details
  • What causes this issue?

    If the activity <ZK>Find Undefined B Segment and Implicit Merges</> is
    called a second time after the mapping has been changed, entries that
    previously required <DS:TX.CNV_20100_TX_BSEGM_PRIOCTRL>B level priority
    control</> may now have become obsolete.

    How to fix this error?

    In the activity <ZK>Maintain B Segment Merges</>, obsolete entries have
    a red traffic light symbol. You need to either delete or explicitly
    accept these entries.
    &ADDITIONAL_HINTS&
    Entries for B priority control are package-dependent, but are deleted
    only during initialization. Entries that have become obsolete get an
    indicator 'O' in table <NP>CNV_20100_BPRIO</>.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message CNV_20100223 - Obsolete entry at B level for G/L account &1 &2 in CoCd &3 ?

    The SAP error message CNV_20100223 "Obsolete entry at B level for G/L account &1 &2 in CoCd &3" typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an issue with the General Ledger (G/L) account entries in the specified company code (CoCd).

    Cause:

    1. Obsolete Entries: The error suggests that there are obsolete or invalid entries for the specified G/L account at the B level (which usually refers to a specific level of detail in the account hierarchy).
    2. Data Inconsistency: There may be inconsistencies in the data being migrated, such as missing or incorrect mappings for the G/L accounts.
    3. Configuration Issues: The G/L account may not be properly configured in the target system, or it may not exist in the chart of accounts being used.

    Solution:

    1. Check G/L Account Configuration:

      • Verify that the G/L account specified in the error message exists in the target system and is correctly configured.
      • Ensure that the account is active and not marked as obsolete or inactive.
    2. Review Migration Data:

      • Check the data being migrated for any inconsistencies or errors. Ensure that the G/L accounts being referenced are valid and correctly mapped.
      • If using a migration template, ensure that the mappings for the G/L accounts are correct.
    3. Adjust Data:

      • If the G/L account is indeed obsolete, consider removing or updating the entries in the source data before migration.
      • If necessary, create new G/L accounts in the target system that correspond to the obsolete accounts, if they are still needed for reporting or historical purposes.
    4. Consult Documentation:

      • Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
    5. Use Transaction Codes:

      • Use transaction codes like OBY6 to check the company code settings and FS00 to review the G/L account settings.
    6. Seek Support:

      • If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration and migration scenario.

    Related Information:

    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
    • Migration Cockpit Documentation: Review the official SAP documentation for the Migration Cockpit, as it may contain specific instructions for handling G/L account issues during migration.
    • Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.

    By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


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