How To Fix CNV_20100158 - Priority set more than once at B level for G/L acct &1 &2 in CoCd &3

CNV_20100158 - Overview

• Message type: E = Error

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

• Message number: 158

• Message text: Priority set more than once at B level for G/L acct &1 &2 in CoCd &3

What causes this issue?

The system found that in the mapping table for
<DS:TX.CNV_20100_TX_BSEGMENT>B segment</> merges the priority indicator
was set more than once for G/L account &V1& &V2& (that will exist after
the merge) in company code &V3&.
Consequently, it is not clear which settings from which company code
will take priority in the merge.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Either set the priority indicator only <ZH>once</> for the given G/L
account in the mapping table for B segment merges, or check the settings
of the new account manually after the merge.

Error message extract from SAP system. Copyright SAP SE.

CNV_20100158 - Details

• The SAP error message CNV_20100158 indicates that there is an issue with the priority settings for a General Ledger (G/L) account during a data migration or conversion process. Specifically, it suggests that the priority for a G/L account has been set more than once at the B level for the specified company code (CoCd).
  
  Cause:
  This error typically arises during the data migration process when:
  
  Duplicate Entries: There are multiple entries for the same G/L account with conflicting priority settings in the migration data.
  Incorrect Mapping: The mapping of G/L accounts from the legacy system to the new system may have been done incorrectly, leading to multiple priorities being assigned.
  
  Configuration Issues: There may be issues in the configuration settings related to the migration or conversion process.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Migration Data:
  
  Review the migration data for the G/L accounts in question. Look for duplicate entries or conflicting priority