Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-EUR (Application Component) European Monetary Union: Euro⤷
CNV_20200_CHECK (Package) Company code merge and rename - Check classes 
Attribute
| Message class |  |
CNV_20200_CHECK | |
| Short Description |  |
Messages for check functions (company code merge) | |
| Message Number |  |
054 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20141030 |
Message Text
Help Document
Diagnosis
There are implicit merges due to the mapping of the company codes.
If according to the mapping a company code is converted to a company code that already exists, these two company codes are merged. If the existing company code is not included in the mapping, this is an implicit merge, that is, a merge that is not defined directly (explicitly) in the mapping, but follows implicitly from the mapping and the existing company code.
Example: Company code A is renamed into B (mapping: A -> B). However company code B exists already and is not meant to be changed into another company code. This would amount to an implicit merge of A and B. For these implicit merges, the same checks as for explicit merges are required (mapping: A -> B; B -> B).
We require that all company codes are included in the mapping, which are part of an identified implicit merge.
System Response
Error
Procedure
You must also add company codes as source values to the mapping if they are target values, and already exist before the conversion.
Procedure for System Administration
History
| Last changed on/by | |
20141030 | SAP |
| SAP Release Created in | 2010_1_620 |
