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

Diagnosis

When checking the G/L accounts you want to merge, the system found that as a result of the chart of accounts change the account will be changed into target account .

However target account already exists in the database.

Target account itself is not used as the source account ( -> XXXX) for another mapping or for a merge of accounts.

This means that account is implicitly merged with existing account at A level.

At B level, however, the mapping ( -> ) will not result in a merge (G/L account number is not changed).

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 the 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 other mapping 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 it is undefined which source account settings the target account will get.

In this case you should check the settings in the A segment (master data in chart of accounts, transaction FSP3) and B segment (master data in company code, transaction FSS3) for the relevant 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