Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 184
Message text: Zielkonto &2 existiert bereits, impliziter Merge durch KtoPl.-Umbenennung
When checking the G/L accounts you want to merge, the system found that
as a result of the chart of accounts change the account &V1& will be
changed into target account &V2&.
However target account &V2& already exists in the database.
Target account &V2& itself is not used as the source account (&V2& ->
XXXX) for another mapping or for a merge of accounts.
This means that account &V1& is implicitly merged with existing account
&V2& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</>.
At <DS:TX.CNV_20100_TX_BSEGMENT>B level</>, however, the mapping (&V1&
-> &V2&) will not result in a merge (G/L account number is not changed).
This has the following consequences. You need:
to find out if the implicit merge is correct from a logical point of
view
to explicitely include the entry &V1& -> &V2& 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 &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 &V1& -> &V2& in the mapping table so
that at least the following entries exist in the mapping table:
&V1& -> &V2&
&V2& -> &V2&
If applicable, any other mapping 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. However then it is undefined which source account settings
the target account &V2& will get.
In this case you should check the settings in the A segment (master data
in chart of accounts, transaction FSP3) and B segment (master data in
company code, transaction FSS3) for the relevant account &V2& 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_20100184
- Zielkonto &2 existiert bereits, impliziter Merge durch KtoPl.-Umbenennung ?Get instant SAP help. Start your 7-day free trial now.
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_20100182
Im Buchungskreis &4 wird der Landeskontenplan &3 implementiert
Was verursacht dieses Problem? According to the mapping table, you want to transfer/restructure the previous operative chart of accounts &V1&am...
CNV_20100185
KtoPl-Merge: Quell-Kto. &1 existiert; impliz. Merge durch KtoPl-Umbenenn.
Was verursacht dieses Problem? As a consequence of the planned chart of accounts merge, implicit account merges will occur as well. When checking t...
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<...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.