SAP ABAP Message Class CNV_20100 Message Number 195 (CoA merge: Source cost element &1 exists; implicit merge by CoA rename)
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 195  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20141030   
Message Text
CoA merge: Source cost element &1 exists; implicit merge by CoA rename
Help Document

Diagnosis

When checking the cost elements to be merged, the system found that as a consequence of the chart of accounts change cost element will be renamed into target cost element .

However another source cost element exists already in the database and will also be renamed into target cost element as a consequence of the chart of accounts change.

This means that cost element will implicitly be merged with the existing cost element at A level (CSKA, A level).

This has the following consequences. You need:

  1. to find out if the implicit merge at A level is correct from a logical point of view.
  2. to explicitely include the entries -> and -> 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 .
    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 B level, the mapping ( -> ) and( -> ) will not result in a merge. (Each cost element exists only once in the controlling area.)

Procedure

Regarding item 2:

Explicitely include the mapping -> and -> in the mapping table so that at least the following entries exist in the mapping table:

  • ->
  • ->
  • If necessary, any others with target cost element .

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 prio indicator for one of the entries with target cost element .

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.

Further notes

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

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