Black Friday is ending this Friday! 40% off with coupon CYBER40 - Sign up here

Close

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.


CNV_20100223 - Details

  • 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.


CNV_20100223 - Related SAP Errors

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