Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 185
Message text: KtoPl-Merge: Quell-Kto. &1 existiert; impliz. Merge durch KtoPl-Umbenenn.
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&.
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 &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.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
CNV_20100185
- KtoPl-Merge: Quell-Kto. &1 existiert; impliz. Merge durch KtoPl-Umbenenn. ?Get instant SAP help. Start your 7-day free trial now.
CNV_20100184
Zielkonto &2 existiert bereits, impliziter Merge durch KtoPl.-Umbenennung
Was verursacht dieses Problem? When checking the G/L accounts you want to merge, the system found that as a result of the chart of accounts change ...
CNV_20100183
Keine Landeskontenplan-Implementierung; keine Aktion erforderlich
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
CNV_20100186
Keine Prioritätsvergabe auf B-Ebene für Sachkonto &1 &2 in BuKrs &3
Was verursacht dieses Problem? The system found that you did not set the priority indicator for the <DS:TX.CNV_20100_TX_BSEGMENT>B segment<...
CNV_20100187
Kontenplanabhängige Stammdaten von Kontenplan &1 in Kontenplan &3 kopiert
Was verursacht dieses Problem? The chart of accounts-specific part of the G/L account master records (table SKA1) of operative chart of accounts &a...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.