How To Fix CNV_20100195 - CoA merge: Source cost element &1 exists; implicit merge by CoA rename

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 195

• Message text: CoA merge: Source cost element &1 exists; implicit merge by CoA rename

What causes this issue?

When checking the cost elements to be merged, the system found that as a
consequence of the chart of accounts change cost element &V1& will be
renamed into target cost element &V3&.
However another source cost element &V2& exists already in the database
and will also be renamed into target cost element &V3& as a consequence
of the chart of accounts change.
This means that cost element &V1& will implicitly be merged with the
existing cost element &V2& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</>
(CSKA, A 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 at A level is correct from a logical
point of view.
to explicitely include the entries &V1& -> &V3& and &V2& -> &V3& 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 &V3&.
As only data for information purposes, such as the creation date and
'created by', is affected, the merge can also be done without setting
the priority indicator.
For cost elements, no check for logical correctness is required at A
level. Here a merge is possible without problems. At
<DS:TX.CNV_20100_TX_BSEGMENT>B level</>, the mapping (&V1& -> &V3&) and
(&V2& -> &V3&) will not result in a merge. (Each cost element exists
only once in the controlling area.)

How to fix this error?

<ZH>Regarding item 2:</>
Explicitely include the mapping &V1& -> &V3& and &V2& -> &V3& in the
mapping table so that at least the following entries exist in the
mapping table:
&V1& -> &V3&
&V2& -> &V3&
If necessary, any others with target cost element &V3&.
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 prio indicator for one of the entries with target cost element
&V3&.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. However then you should check the A segment settings in table
CSKA (cost elements - chart of accounts-specific data) for the relevant
cost element after the conversion.
&ADDITIONAL_HINTS&
The priority indicator must not be set more than <ZH>once</> for all
merges to a given target account. This is also valid for cross-chart of
accounts merges.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100195 - CoA merge: Source cost element &1 exists; implicit merge by CoA rename ?

  The SAP error message CNV_20100195 is related to the conversion process during a Chart of Accounts (CoA) merge. This error indicates that there is a conflict with cost elements during the merging of different Chart of Accounts. Specifically, it means that a source cost element already exists in the target Chart of Accounts, and the system is attempting to perform an implicit merge due to a rename of the CoA.
  Cause:
  
  Duplicate Cost Elements: The error arises when the same cost element exists in both the source and target CoA. This can happen if the same cost element is defined in both CoAs with the same or different characteristics.
  CoA Renaming: The implicit merge is triggered by the renaming of the CoA, which leads to conflicts in the cost element definitions.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify Conflicting Cost Elements:
  
  Use transaction codes like SE16 or SE11 to check the cost elements in both the source and target CoAs.
  Identify the specific cost element that is causing the conflict (indicated by &1 in the error message).
  
  
  
  Review CoA Mapping:
  
  Check the mapping of the source and target CoAs to ensure that there are no unintended overlaps or duplicates.
  Adjust the mapping if necessary to avoid conflicts.
  
  
  
  Rename or Merge Cost Elements:
  
  If the cost elements are indeed duplicates, consider renaming or merging them appropriately to eliminate the conflict.
  Ensure that the cost elements in the target CoA are unique and do not overlap with those in the source CoA.
  
  
  
  Adjust Conversion Settings:
  
  Review the settings in the conversion program to ensure that it is configured correctly for the CoA merge.
  You may need to adjust the settings to handle duplicates more effectively.
  
  
  
  Test the Changes:
  
  After making the necessary adjustments, run the conversion process again in a test environment to ensure that the error is resolved.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the CoA merge process for additional guidance and best practices.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (for CoA settings) and OKB9 (for cost element settings).
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional insights into handling CoA merges.
  Backup Data: Always ensure that you have a backup of your data before making significant changes to the CoA or cost elements.
  
  By following these steps, you should be able to resolve the CNV_20100195 error and successfully complete the CoA merge process.