Do you have any question about this error?
Message type: E = Error
Message class: CNV_20600_CHECK - Messages for Check classes
Message number: 055
Message text: Implicit merge into target company code for number assignment &1
<DS:TX.CNV_MBT_IMPLICIT_MERGE>Implicit merge</> into target company code
for number assignment &V1&
If according to the mapping a company code for number assignment is
converted to a company code for number assignment that already exists,
these two company codes for number assignment are merged. If the
existing company code for number assignment is not included in the
mapping, this is an <DS:TX.CNV_MBT_IMPLICIT_MERGE>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 for number assignment.
Example: Company code for number assignment A is renamed into B
(mapping: A -> B). However company code for number assignment B exists
already and is not meant to be changed into another company code for
number assignment. This would amount to an implicit merge of A and B.
For these <DS:TX.CNV_MBT_IMPLICIT_MERGE>implicit merges</>, the same
checks as for explicit merges are required (mapping: A -> B; B -> B).
We require that all company codes for number assignment are included in
the mapping, which are part of an identified
<DS:TX.CNV_MBT_IMPLICIT_MERGE>implicit merge</>.
Error
You must add company code for number assignment &V1& as source value to
the mapping.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CNV_20600_CHECK055 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 implicit merging of number assignments into a target company code.
Cause:
The error can arise due to several reasons, including:
- Duplicate Number Ranges: The target company code may have number ranges that conflict with those being imported or merged from the source system.
- Incorrect Configuration: The configuration settings for number ranges in the target company code may not be set up correctly to accommodate the incoming data.
- Data Integrity Issues: There may be inconsistencies or integrity issues in the data being migrated, such as missing or invalid entries.
- Missing Customizing Settings: The necessary customizing settings for number assignment in the target company code may not be properly defined.
Solution:
To resolve the error, you can take the following steps:
Check Number Ranges:
- Verify the number ranges defined in the target company code. Ensure that they do not overlap with the number ranges from the source system.
- Adjust the number ranges in the target system if necessary to avoid conflicts.
Review Configuration:
- Ensure that the configuration for number assignment in the target company code is correctly set up. This includes checking the settings in transaction codes like SNRO (Number Range Objects) and OBA7 (Define Number Ranges for Document Types).
Data Validation:
- Validate the data being migrated to ensure that there are no duplicates or invalid entries. Clean up the data if necessary before attempting the migration again.
Customizing Settings:
- Check if all necessary customizing settings related to number assignment are in place. This may include settings for document types, number ranges, and other related configurations.
Consult Documentation:
- Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
Testing:
- After making the necessary adjustments, perform a test migration with a smaller dataset to ensure that the issue has been resolved before proceeding with the full migration.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to successfully complete your data migration.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
CNV_20600_CHECK054 Implicit merges due to mapping of company codes for number assignment
What causes this issue? There are <DS:TX.CNV_MBT_IMPLICIT_MERGE>implicit ...
CNV_20600_CHECK053 Temp. dupl. possible due to mapping of comp.codes for no. assignm. &1, &2
What causes this issue? <DS:TX.CNV_MBT_TEMP_DUPLICATES>Temporary duplicat...
CNV_20600_CHECK056 Temporary duplicates possible due to mapping of company codes
What causes this issue? <DS:TX.CNV_MBT_TEMP_DUPLICATES>Temporary duplicat...
CNV_20600_CHECK057 Temporary duplicates possible due to mapping of company codes &1, &2
What causes this issue? <DS:TX.CNV_MBT_TEMP_DUPLICATES>Temporary duplicat...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.