Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 033
Message text: &1 -> &2 is supporting scenario; renaming accounts is not permitted
Normally, it does not make sense to copy chart of accounts &V1& into
the same chart of accounts &V1&.
BUT:
If a chart of account X is merged into an existing chart of accounts
&V1&, the customer may want to make sure that the accounts and cost
elements from the existing target chart of accounts &V1& are given
priority in merges.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
This requirement can be implemented by mapping &V1& -> &V2& with Copy =In a mere priority scenario, no merges of accounts or cost elements are
allowed. A check is made to ensure this.
For priority control, you must set priority = 'X' only for accounts or
cost elements with the same name:
Example:
<ZH>OLD_acct NEW_acct Priority</>
10000 10000 X
However it was found that you plan to do a rename from &V3& to &V4&.
This is not allowed.
Change the mapping accordingly or delete the COPY indicator in the
mapping maintenance on central chart of accounts level.
&ADDITIONAL_HINTS&
If you have a priority scenario, it is also <zh>not</> allowed to
maintain participating company codes.
Error message extract from SAP system. Copyright SAP SE.
CNV_20100033
- &1 -> &2 is supporting scenario; renaming accounts is not permitted ?The SAP error message CNV_20100033 typically occurs during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an attempt to rename accounts in a scenario that does not support this action.
Cause:
The error message suggests that the system is trying to rename an account (or accounts) in a migration scenario where renaming is not allowed. This can happen due to several reasons:
- Unsupported Migration Scenario: The migration scenario you are using does not permit renaming of accounts. Some scenarios are designed to only allow the creation of new accounts or the mapping of existing accounts without renaming.
- Configuration Issues: There may be configuration settings in the migration cockpit or the source system that do not allow for account renaming.
- Data Mapping Errors: The mapping of accounts in the migration process may be incorrectly set up, leading to attempts to rename accounts instead of mapping them correctly.
Solution:
To resolve this error, consider the following steps:
Check Migration Scenario: Verify that you are using the correct migration scenario that supports the actions you intend to perform. If renaming is not supported, you may need to adjust your approach.
Review Mapping Configuration: Go through the mapping configuration in the migration cockpit. Ensure that you are mapping existing accounts correctly without attempting to rename them.
Consult Documentation: Refer to the SAP documentation for the specific migration scenario you are using. This documentation will provide insights into what actions are permitted and how to properly configure the migration.
Use Alternative Methods: If renaming is essential for your migration, consider using alternative methods or tools that allow for account renaming, or adjust your data model to accommodate the restrictions of the current migration scenario.
Seek Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide guidance based on your specific system configuration and migration requirements.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
CNV_20100032
&1 is a group CoA to which no company codes are assigned directly
What causes this issue? According to the mapping table, you want to convert the group chart of accounts &V1&. Group charts of accounts are as...
CNV_20100031
Operative CoA &2 has CoA &1 as group CoA
What causes this issue? The program found that you want to rename or restructure the group chart of accounts &V1&.System Response A check sh...
CNV_20100034
&1 -> &2 cannot have participating company codes; see long text
What causes this issue? Copying chart of accounts &V1& into chart of accounts &V1& (same name!) does not make sense. However if you m...
CNV_20100035
For CoA &1, CoCd &3 was indicated for CoAr &2, while CoCd &4 was not
What causes this issue? The chart of accounts is defined at controlling area level. Consequently, all company codes that belong to a given controllin...
Click on this link to search all SAP messages.