Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: CNV20200 - Messages for development class CNV_20200
Message number: 390
Message text: Ref. company code &1 merged into target CoCd &2 => special priority
Reference company code &V1& is merged into the existing company code
&V2&.
By default, the settings from the reference company code would take
priority when table keys become identical because of the conversion.
In this case, however, the target company code exists already, and as a
rule special settings and data from this company code should be
transferred to the target.
These are the following:
VAT registration number (T001-STCEG)
Additional information regarding the company code (table T001Z)
Address data for the company code (ADR* tables)
Name of the related company (table T880)
Error message
Tables for which the settings of the target company code should take
priority must have the priority routine CNV_20200_PRIO_BUKRS_TARGET
assigned.
The priority routine CNV_20200_PRIO_AD_OBJKEY evaluates the priority
field for TABNAME=T001 in accordance with the logic of routine
CNV_20200_PRIO_BUKRS_TARGET.
Error message extract from SAP system. Copyright SAP SE.
CNV20200390
- Ref. company code &1 merged into target CoCd &2 => special priority ?The SAP error message CNV20200390 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 a conflict or issue related to the merging of company codes (CoCd) during the data migration process.
Cause:
- Merging Company Codes: The error suggests that the source company code (&1) is being merged into the target company code (&2). This can happen if there are overlapping or conflicting data entries between the two company codes.
- Data Inconsistencies: There may be inconsistencies in the data being migrated, such as duplicate entries, missing references, or incorrect configurations.
- Configuration Issues: The configuration settings for the migration process may not be set up correctly, leading to conflicts during the merging of company codes.
Solution:
- Review Migration Settings: Check the migration settings in the SAP S/4HANA Migration Cockpit to ensure that the company codes are correctly defined and that the merging process is intended.
- Data Validation: Validate the data in both the source and target company codes to identify any inconsistencies or duplicates. Clean up the data as necessary before attempting the migration again.
- Adjust Mapping: If the merging of company codes is not intended, adjust the mapping settings to ensure that the data is directed to the correct company codes without merging.
- Consult Documentation: Refer to the SAP documentation related to the specific migration tool you are using for detailed guidance on handling company code merges and related errors.
- Seek Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide assistance based on the specific context of your migration project.
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 the migration process.
Get instant SAP help. Sign up for our Free Essentials Plan.
CNV20200389
Duplicates for &1: &2
What causes this issue? The given mapping will lead to duplicates. This means that &V1& will have the same ID. &V2& is the target obj...
CNV20200388
Reference CoCd &1 and accounting code with same name but diff. target val
What causes this issue? The reference company code &V1& and the related treasury accounting code &V3& have the same ID now, but diffe...
CNV20200392
Customizing for rental agreement no.s in CoCd=&1 missing in table TIPZB
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV20200394
Structure of rental agreement no. &1 in CoCd=&2 not yet considered
What causes this issue? Conversion routine CNV_20200_LEASE_OUT_NO in program include CNV_20200_P_IMMO may have to be enhanced, because the given stru...
Click on this link to search all SAP messages.