Hierarchy
⤷ 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 | 215 | ||
Documentation status | Space: object requires documentation | ||
Authorization check Error Message | |||
Changed On | 20141030 |
Message Text
Help Document
Diagnosis
When checking the cost elements that will be merged, the system found that target cost element will be converted into (mapping -> ).
Another source cost element exists already in the database and will also be transferred to target cost element as a consequence of the chart of accounts change.
This means that cost element will implicitly be merged with existing cost element at A level as well as at B level.
This has the following cnsequences. You need:
- to find out if the implicit merge is correct from a logical point of view
- to explicitely include the entry -> to the mapping
- consider the priority indicator. If the priority indicator is not set, it is not clear which settings will take priority when cost elements 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 cost element .
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) as well as the B segment settings (master data in controlling area, transaction KA02) for the cost element 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-charts of accounts merges.
History
Last changed on/by | 20141030 | SAP | |
SAP Release Created in |