How To Fix CNV_20100094 - Target cost element &2 exists, implicit merge by rename of cost element

CNV_20100094 - Overview

• Message type: E = Error

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

• Message number: 094

• Message text: Target cost element &2 exists, implicit merge by rename of cost element

What causes this issue?

When the cost elements that you plan to merge were checked, it was found
that target cost element &V2& (mapping &V1& -> &V2&) already exists on
the database.
However target cost element &V2& is not used as a source cost element (
&V2& -> XXXX) for another mapping relation.
This means that cost element &V1& is in fact merged with existing cost
element &V2& at chart of accounts-dependent cost element master data
level (CSKA, A level) as well as at controlling area-dependent cost
element master data level (CSKB, B level).

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

This has the following consequences. You need:
to find out if the implicit merge is correct from a logical point of
view
to explicitely include the entry &V2& -> &V2& to the mapping
to consider the priority indicator. If the priority indicator is not
set, it is not clear which settings will take priority when cost
elements &V1& and &V2& are merged into &V2&.

How to fix this error?

<ZH>Regarding item 2:</>
Include the mapping &V2& -> &V2& into the mapping table so that at least
the following entries exist in the mapping table:
&V1& -> &V2&
&V2& -> &V2&
If applicable, any other mapping with target cost element &V2&.
This allows the system to check the merge for logical correctness.
A troubleshooting activity is associated to this activity which supports
you in creating the required mapping entries to resolve the implicit
merges.
<ZH>Regarding item 3:</>
Set the priority indicator for one of the entries for which &V2& is the
target cost element.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. However then you should check the settings in A segment
(master data in chart of accounts, transaction FSP3) and B segment
(master data in controlling area, transaction FSS3) for the relevant
cost element &V2& after the conversion.
&ADDITIONAL_HINTS&
The priority indicator must not be set more than <ZH>once</> for all
merges to a given target cost element. This is also valid for
cross-chart of accounts merges.

Error message extract from SAP system. Copyright SAP SE.

CNV_20100094 - Details

• The SAP error message CNV_20100094 indicates that during a data migration or conversion process, a target cost element already exists in the system. This situation arises when the system attempts to create a new cost element that has the same identifier as an existing one, leading to an implicit merge by renaming the cost element.
  
  Cause:
  
  Duplicate Cost Element: The error occurs because the target cost element (identified by &2) already exists in the system. This can happen during data migration when the source system has cost elements that conflict with those in the target system.
  Data Migration Process: The error is often encountered during the execution of a migration project, particularly when using SAP's Migration Cockpit or other data migration tools.
  
  
  Solution:
  
  
  Review Existing Cost Elements: Check the existing cost elements in the target system to understand why the conflict is occurring. You can do this by navigating to the relevant transaction (e.g., KS01