How To Fix CNV_40300018 - Neue Anlagenklasse &2 bereits vorhanden; impliz.Zusammführung ü.KlassName

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_40300 - Message class for package 40300 (ANLKL)

• Message number: 018

• Message text: Neue Anlagenklasse &2 bereits vorhanden; impliz.Zusammführung ü.KlassName

Was verursacht dieses Problem?

When the asset classes that you plan to merge were checked, it was found
that new asset class &V2& (mapping &V1& -> &V2&) already exists in the
database.
However the new asset class &V2& is not used as an old asset class (
&V2& -> XXXX) for another mapping relation.
This means that asset class &V1& is in fact merged with the existing
asset class &V2&.

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 is correct from a logical point of
view
to explicitely include the entry &V2& -> &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 asset class &V1& and &V2&
are merged into &V2&.

Wie behebe ich diesen Fehler?

<ZH>Regarding item 2:</>
Explicitely include the mapping &V2& -> &V2& into 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 the new asset class &V2&.
<ZH>Regarding item 3:</>
Set the priority indicator for one of the entries for which &V2& is the
new asset class.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. However then it is undefined which old asset class settings
the new asset class &V2& will get. In this case you should check the
asset class settings (transaction OAOA) for the relevant asset class
&V2& after the conversion.
&ADDITIONAL_HINTS&
The priority indicator must not be set more than <ZH>once</> for all
merges to a given asset class.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE