SAP ABAP Message Class CNV_20100 Message Number 094 (Target cost element &2 exists, implicit merge by rename of cost element)
Hierarchy
☛ DMIS (Software Component) DMIS 2011_1
   ⤷ CA-GTF-BS (Application Component) Business Application Support
     ⤷ CNV_20100 (Package) CNCC: Chart of accounts conversion
Attribute
Message class CNV_20100  
Short Description Messageclass for chart of account conversion    
Message Number 094  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20141030   
Message Text
Target cost element &2 exists, implicit merge by rename of cost element
Help Document

Diagnosis

When the cost elements that you plan to merge were checked, it was found that target cost element (mapping -> ) already exists on the database.

However target cost element is not used as a source cost element ( -> XXXX) for another mapping relation.

This means that cost element is in fact merged with existing cost element at chart of accounts-dependent cost element master data level (CSKA, A level) as well as at controlling area-dependent cost element master data level (CSKB, B level).

This has the following consequences. You need:

  1. to find out if the implicit merge is correct from a logical point of view
  2. to explicitely include the entry -> to the mapping
  3. to consider the priority indicator. If the priority indicator is not set, it is not clear which settings will take priority when cost elements and are merged into .

Procedure

Regarding item 2:

Include the mapping -> into the mapping table so that at least the following entries exist in the mapping table:

  • ->
  • ->
  • If applicable, any other mapping with target cost element .

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.

Regarding item 3:

Set the priority indicator for one of the entries for which is the target cost element.

Note

It is possible to do the conversion without setting the priority indicator. However then you should check the settings in A segment (master data in chart of accounts, transaction FSP3) and B segment (master data in controlling area, transaction FSS3) for the relevant cost element after the conversion.

Further notes

The priority indicator must not be set more than once for all merges to a given target cost element. This is also valid for cross-chart of accounts merges.

History
Last changed on/by 20141030  SAP 
SAP Release Created in