SAP ABAP Message Class CNV_20100 Message Number 216 (Source account &3 already exists; implicit merge)
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 216  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20141030   
Message Text
Source account &3 already exists; implicit merge
Help Document

Diagnosis

When checking the G/L accounts that will be merged, the system found that the mapping -> will result in an implicit merge with source account .

The reason is that source account is not itself a source account ( -> XXXX) for another mapping.

Consequently, account would be merged implicitly with existing account at A level as well as at B level.

This has the following consequences. You need:

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

Procedure

Regarding item 2:

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

  • ->
  • ->
  • If applicable, any others with target account .

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 with target account .

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, transaction FSP3) and B segment settings (master data in company code, transaction FSS3) for the affected account after the conversion.

Further notes

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

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