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


CNV_20100223 - Overview

  • 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: 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). Data Inconsistency: There may be inconsistencies in the data being migrated, such as missing or incorrect mappings for the G/L accounts.
    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: Check G/L Account Configuration: Verify that the G/L account specified in the error message exists in

    Already have an account? Login here!




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
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author