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

Diagnosis

The planned chart of accounts merge will lead to implicit merges of accounts.

The check of the G/L accounts that will be merged showed that source account will be converted into (mapping -> ).

Another source account already exists in the database and will also be merged into target account as a consequence of the chart of accounts change into .

This means that account will implicitly be merged with existing account at A level. At B level, the mapping will not result in a merge because the charts of accounts that will be merged are necessarily assigned to different company codes.

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 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 necessary, 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. However then you should check the A segment settings (master data in chart of accounts, transaction FSP3) for the account 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