How To Fix CNV_20100215 - KtoPl-Merge: Quell-Kstar &1 existiert; impliz. Merge durch Kstarumbenenn.


SAP Error Message - Details

  • 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.

  • Show details Hide details
  • Was verursacht dieses Problem?

    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:
    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
    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 &V3& are merged into &V2&

    Wie behebe ich diesen Fehler?

    <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


Smart SAP Assistant

  • Was ist die Ursache und Lösung für den SAP Fehler CNV_20100215 - KtoPl-Merge: Quell-Kstar &1 existiert; impliz. Merge durch Kstarumbenenn. ?




    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Zugehörige SAP-Fehlermeldungen

Klicken Sie auf die Links unten, um die folgenden verwandten Nachrichten anzuzeigen:

Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant