Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 216
Message text: Source account &3 already exists; implicit merge
When checking the G/L accounts that will be merged, the system found
that the mapping &V1& -> &V2& will result in an
<DS:TX.CNV_20100_TX_IMPLICITMERGE>implicit merge</> with source account
&V3&.
The reason is that source account &V3& is not itself a source account (
&V3& -> XXXX) for another mapping.
Consequently, account &V1& would be merged implicitly with existing
account &V3& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</> as well as at
<DS:TX.CNV_20100_TX_BSEGMENT>B level</>.
This has the following consequences. You need:
to find out if this implicit merge is correct from a logical point of
view
to explicitely include the entry &V3& -> &V2& to the mapping
consider the priority indicator. If the priority indicator is not set,
it is not clear which settings will take priority when accounts &V1& and
&V3& are merged into &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
<ZH>Regarding item 2:</>
Explicitely include the mapping &V3& -> &V2& in the mapping table so
that at least the following entries exist in the mapping table:
&V1& -> &V2&
&V3& -> &V2&
If applicable, any others with target account &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 with target account
&V2&.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. In this case you should check the A segment settings (master
data in chart of accounts, transaction FSP3) and B segment settings
(master data in company code, transaction FSS3) for the affected account
&V2& after the conversion.
&ADDITIONAL_HINTS&
The priority indicator must not be set more than <ZH>once </>for all
merges to a given account. This is also valid for cross-chart of
accounts merges.
Error message extract from SAP system. Copyright SAP SE.
CNV_20100216
- Source account &3 already exists; implicit merge ?The SAP error message CNV_20100216: Source account &3 already exists; implicit merge 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 attempt to create a source account that already exists in the target system, leading to an implicit merge of accounts.
Cause: Duplicate Source Accounts: The error arises when the migration process encounters a source account that has already been defined in the target system. This can happen if: The same account is being migrated multiple times. There are inconsistencies in the source data leading to duplicate entries. The mapping of accounts from the source to the target system is not correctly defined. Data Preparation Issues: If the data preparation phase did not adequately clean or deduplicate the source data, it could lead to multiple entries for the same account.
Solution: Review Source Data: Check the source data for duplicates. Ensure
Get instant SAP help. Sign up for our Free Essentials Plan.
CNV_20100215
CoA merge: Source cost element &1 exists; implicit merge by CostEl rename
What causes this issue? When checking the cost elements that will be merged, the system found that target cost element &V1& will be converted...
CNV_20100214
Set &1 &2 &3 is too long after conversion
What causes this issue? Set &V4& that will be created during the conversion has more than 12 digits.System Response This may lead to errors ...
CNV_20100217
Source cost element &3 already exists; implicit merge
If applicable, any others with target cost element &V2&. This allows the system to check the merge for logical correctness. A troubleshooting...
CNV_20100218
Implicit merges found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.