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 |  |
194 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20141030 |
Message Text
Help Document
Diagnosis
When checking the cost elements that you plan to merge, the system found that as a result of the chart of accounts change cost element will be changed into target cost element .
However target cost element already exists in the database.
Target cost element itself is not used as a source cost element ( -> XXXX) for another mapping relation or for an account merge.
This means that cost element is in fact merged with existing cost element at A level.
If the priority indicator is not set, it is not clear which settings will take priority when cost elements and are merged into. As the affected fields contain only additional information, such as the creation date and the person who created he cost element, it is acceptable to merge the cost elements without a priority.
For cost elements, a check for logical correctness at A level is required. A merge can be done without any problems. At B level, the mapping ( -> ) will not result in a merge (each cost element exists only once in the controlling area). For this reason, it is not necessary to make any temporary additions to the mapping table.
Procedure
This message is meant to inform you that you are doing an implicit merge of cost elements by changing the 'chart of accounts' field at A level.
If you want to define which settings will take priority at A level, include the mapping -> in the mapping table so that it includes at least the following entries:
- ->
- ->
- If necessary, any other mapping with target cost element .
Set the prio indicator for one of the entries with target cost element .
Note
As described above, you can also do without these entries. In this case, you may want to check the settings for A segment (table CSKA, chart of accounts-dependent data for cost elements) for the relevant cost element after the conversion.
Further notes
Note that you must not set the priority indicator 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 |
