How To Fix CNV_20100195 - KtoPl-Merge: Quellkostenart &1 exist.; impliz.Merge durch KtoPl-Umbenenn.

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20100 - Messageclass for chart of account conversion

• Message number: 195

• Message text: KtoPl-Merge: Quellkostenart &1 exist.; impliz.Merge durch KtoPl-Umbenenn.

Was verursacht dieses Problem?

When checking the cost elements to be merged, the system found that as a
consequence of the chart of accounts change cost element &V1& will be
renamed into target cost element &V3&.
However another source cost element &V2& exists already in the database
and will also be renamed into target cost element &V3& as a consequence
of the chart of accounts change.
This means that cost element &V1& will implicitly be merged with the
existing cost element &V2& at <DS:TX.CNV_20100_TX_ASEGMENT>A level</>
(CSKA, A level).

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

This has the following consequences. You need:
to find out 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 cost
elements &V1& and &V2& are merged into &V3&.
As only data for information purposes, such as the creation date and
'created by', is affected, the merge can also be done without setting
the priority indicator.
For cost elements, no check for logical correctness is required at A
level. Here a merge is possible without problems. At
<DS:TX.CNV_20100_TX_BSEGMENT>B level</>, the mapping (&V1& -> &V3&) and
(&V2& -> &V3&) will not result in a merge. (Each cost element exists
only once in the controlling area.)

Wie behebe ich diesen Fehler?

<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 necessary, any others with target cost element &V3&.
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 prio indicator for one of the entries with target cost element
&V3&.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. However then you should check the A segment settings in table
CSKA (cost elements - chart of accounts-specific data) for the relevant
cost element 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