Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 215
Message text: KtoPl-Merge: Quell-Kstar &1 existiert; impliz. Merge durch Kstarumbenenn.
When checking the cost elements that will be merged, the system found
that target cost element &V1& will be converted into &V2& (mapping &V1&
-> &V2&).
Another source cost element &V3& exists already in the database and will
also be transferred to target cost element &V2& as a consequence of the
chart of accounts change.
This means that cost element &V1& will implicitly be merged with
existing cost element &V3& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</> as
well as at <DS:TX.CNV_20100_TX_BSEGMENT>B level</>.
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
This has the following cnsequences. You need:<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 cost
element &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) as well as the B segment settings (master
data in controlling area, transaction KA02) for the cost element &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-charts of
accounts merges.
Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
CNV_20100215
- KtoPl-Merge: Quell-Kstar &1 existiert; impliz. Merge durch Kstarumbenenn. ?Get instant SAP help. Start your 7-day free trial now.
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_20100213
Set-Daten müssen noch in transparente Tabellen übertragen werden
Was verursacht dieses Problem? In Release 3.x, the sets were stored in tables T800S, T800X, T800Y and SETDATA. From SAP release 4.0 onwards, sets a...
CNV_20100216
Ausgangskonto &3 existiert bereits; impliziter Merge
Was verursacht dieses Problem? When checking the G/L accounts that will be merged, the system found that the mapping &V1& -> &V2&...
CNV_20100217
Quell-Kostenart &3 existiert bereits; implizite Zusammenführung
Was verursacht dieses Problem? When checking the secondary cost elements that will be merged, the system found that the mapping &V1& -> ...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.