How To Fix CNV_20100185 - CoA merge: Source account &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: 185

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

What causes this issue?

As a consequence of the planned chart of accounts merge, implicit
account merges will occur as well.
When checking the G/L accounts that will be merged, the system found
that account &V1& will be transferred to target account &V3& when the
chart of accounts is changed.
Another source account &V2& already exists on the database and will also
be transferred to target account &V3& when chart of accounts &V4& is
changed.
This means that account &V1& is implicitly merged with account &V2& at
<DS:TX.CNV_20100_TX_ASEGMENT>A level</>.
At <DS:TX.CNV_20100_TX_BSEGMENT>B level</>, the mapping (&V1& -> &V3&)
and (&V2& -> &V3&) will not result in a merge. (G/L account number will
not be changed.)
This has the following consequences. You need:
to check 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 the accounts
&V1& and &V2& are merged into &V3&.

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?

<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 applicable, any other mapping entries with target account &V3&.
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 with target account
&V3&.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. However then you should check the settings in the A segment
(master data in chart of accounts, transaction FSP3) for account &V3&
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_20100185 - CoA merge: Source account &1 exists; implicit merge by CoA rename ?

  The SAP error message CNV_20100185 is related to the conversion of Chart of Accounts (CoA) during a data migration or system upgrade process. This error typically occurs when there is an attempt to merge accounts in the Chart of Accounts, and the source account already exists in the target CoA. The message indicates that an implicit merge is being performed due to the renaming of the CoA.
  Cause:
  
  Duplicate Accounts: The source account you are trying to migrate or merge already exists in the target Chart of Accounts.
  CoA Renaming: The system is attempting to rename the source account to avoid duplication, which leads to the implicit merge.
  Data Migration Issues: This can occur during data migration processes where accounts from different CoAs are being consolidated.
  
  Solution:
  
  Review the CoA Mapping: Check the mapping of accounts between the source and target CoA to ensure that there are no unintended duplicates.
  Adjust the Source Data: If possible, modify the source data to avoid conflicts with existing accounts in the target CoA.
  Manual Merge: If the implicit merge is not desirable, consider manually merging the accounts before the migration process.
  Consult Documentation: Refer to SAP documentation or guides related to the specific migration tool you are using (e.g., SAP S/4HANA Migration Cockpit) for detailed steps on handling CoA merges.
  Testing: Conduct thorough testing in a development or sandbox environment to identify and resolve any potential conflicts before executing the migration in the production environment.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 (for managing CoA) and OBD4 (for account determination).
  SAP Notes: Check for any SAP Notes related to the error message for additional guidance or patches that may address the issue.
  Migration Tools: If you are using specific migration tools (like SAP S/4HANA Migration Cockpit), ensure you are following the best practices and guidelines provided by SAP for CoA migration.
  
  By addressing the root cause of the error and following the suggested solutions, you should be able to resolve the issue effectively.