Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 205
Message text: KtoPl-Merge: Quell-Kto. &1 exist.; impliz. Merge durch Kontoumbenennung
The planned chart of accounts merge will lead to implicit merges of
accounts.
The check of the G/L accounts that will be merged showed that source
account &V1& will be converted into &V2& (mapping &V1& -> &V2&).
Another source account &V3& already exists in the database and will also
be merged into target account &V2& as a consequence of the chart of
accounts change into &V4&.
This means that account &V1& will implicitly be merged with existing
account &V3& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</>. At
<DS:TX.CNV_20100_TX_BSEGMENT>B level</>, the mapping will not result in
a merge because the charts of accounts that will be merged are
necessarily assigned to different company codes.
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 &V3& -> &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 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 necessary, 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. However then you should check the A segment settings (master
data in chart of accounts, transaction FSP3) for the 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_20100205
- KtoPl-Merge: Quell-Kto. &1 exist.; impliz. Merge durch Kontoumbenennung ?Get instant SAP help. Start your 7-day free trial now.
CNV_20100204
Zu implement. Landeskontenpl. &3 ist selbst Ziel einer anderen Umstellung
Was verursacht dieses Problem? You are going to implement the country-specific chart of accounts &V3& for target chart of accounts &V2&...
CNV_20100203
Merge auf A/B-Ebene: Keine Prioritätssteuerung bei Merge auf Kostenart &1
Was verursacht dieses Problem? It was found that two or more old cost elements ae mapped to target &V1& , but the priority indicator is set...
CNV_20100206
Stammdaten von KtoPl &1 für Implementierung von LandktoPl &2 gesichert
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
CNV_20100207
Landeskontenplan &1 für Buchungskreis &2 implementiert
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.