Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 152
Message text: Undefined merge to account &1 in company code &2
When checking the merges to target account &V1&, the system found that
the priority account &V3& does not exist in company code &V2&.
However at least two other merges to this target account are planned in
this company code.
As the priority account does not exist in this company code, it is not
clear from which account (from the other merges) the settings will be
transferred to this account.
Not yet defined
Error message extract from SAP system. Copyright SAP SE.
CNV_20100152
- Undefined merge to account &1 in company code &2 ?The SAP error message CNV_20100152 Undefined merge to account &1 in company code &2 typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an issue with the mapping of accounts during the merge process, specifically that the target account (merge to account) has not been defined in the system for the specified company code.
Cause:
- Missing Configuration: The merge-to account specified in the error message is not defined in the system for the given company code. This could be due to a configuration oversight during the setup of the migration or conversion process.
- Incorrect Mapping: The mapping of accounts may not have been set up correctly, leading to references to accounts that do not exist in the target system.
- Data Issues: There may be issues with the source data that are causing the migration tool to reference an invalid or non-existent account.
Solution:
Define the Merge-to Account:
- Go to the SAP transaction code OBY6 (or the relevant configuration transaction) to check the account settings for the specified company code.
- Ensure that the merge-to account (account &1) is defined and active in the system.
Check Mapping Configuration:
- Review the mapping configuration in the migration tool to ensure that all accounts are correctly mapped.
- If necessary, update the mapping to point to the correct accounts that exist in the target system.
Data Validation:
- Validate the source data to ensure that it does not reference any accounts that are not defined in the target system.
- Clean up any inconsistencies in the source data before attempting the migration again.
Consult Documentation:
- Refer to the SAP documentation for the specific migration tool you are using to ensure that all steps have been followed correctly.
Testing:
- After making the necessary changes, perform a test migration to verify that the issue has been resolved.
Related Information:
By following these steps, you should be able to resolve the error CNV_20100152 and successfully complete your data migration or conversion process.
Get instant SAP help. Start your 7-day free trial now.
CNV_20100151
CoA merge scenario due to implicit merge to existing CoA &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100150
Object type &1 is unknown for &2 &3; create/change not possible
What causes this issue? The entry &V1& is not valid for the object type (ART).System Response In the text mapping, specify in field ART whet...
CNV_20100153
Select only one column
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100154
Priority indicator is set more than once, which is not allowed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.