Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 216
Message text: Ausgangskonto &3 existiert bereits; impliziter 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&.
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
<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.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
CNV_20100216
- Ausgangskonto &3 existiert bereits; impliziter Merge ?Get instant SAP help. Start your 7-day free trial now.
CNV_20100215
KtoPl-Merge: Quell-Kstar &1 existiert; impliz. Merge durch Kstarumbenenn.
Was verursacht dieses Problem? When checking the cost elements that will be merged, the system found that target cost element &V1& will be ...
CNV_20100214
Set &1 &2 &3 ist nach der Umstellung zu lang
Was verursacht dieses Problem? Set &V4& that will be created during the conversion has more than 12 digits.Systemantwort This may lead to...
CNV_20100217
Quell-Kostenart &3 existiert bereits; implizite Zusammenführung
If applicable, any others with target cost element &V2&. This allows the system to check the merge for logical correctness. A troubleshooting...
CNV_20100218
Implizite Zusammenführungen gefunden
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.