Do you have any question about this error?
Message type: E = Error
Message class: CNV - Conversion: Messages for Conversion Services (CNCC)
Message number: 790
Message text: Duplicate processing type for table &1 was not maintained
A key field of table &V1& is converted.
However the duplicate processing type indicator for this table has not
been maintained.
If you have a merge scenario, duplicate records may occur while this
table is being converted. If the duplicate processing type is not set
and duplicate records occur, the conversion program terminates.
If necessary, maintain the duplicate processing type for the
corresponding table in activity <ZK>Settings for new conversion-Relevant
tables and Fields</>.
&TECHNICAL-INFO&
Duplicate handling type is stored in column SUMUP of table CNVTABLES.
For available values see corresponding <DS:DE.CNV_SUM>F1-help document
</>.
Error message extract from SAP system. Copyright SAP SE.
CNV790
- Duplicate processing type for table &1 was not maintained ?The SAP error message "CNV790 Duplicate processing type for table &1 was not maintained" typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools. This error indicates that there is a duplicate entry for a processing type associated with a specific table in the migration configuration.
Cause:
- Duplicate Entries: The error is primarily caused by having multiple entries for the same processing type for a specific table in the migration configuration. This can happen if the configuration was not set up correctly or if there were changes made that were not properly reflected in the migration settings.
- Incorrect Configuration: The configuration for the data migration might not have been maintained correctly, leading to conflicts in processing types.
- Data Model Changes: If there have been changes in the data model or the migration structure, it could lead to inconsistencies that trigger this error.
Solution:
- Check Configuration: Review the migration configuration for the specific table mentioned in the error message. Look for duplicate entries for processing types and remove or correct them.
- Maintain Processing Types: Ensure that the processing types for the table are correctly maintained. Each processing type should be unique for the table in question.
- Use Transaction Codes: You can use transaction codes like
LTMC
(for Migration Cockpit) orLTMOM
(for Migration Object Modeler) to check and adjust the migration settings.- Consult Documentation: Refer to SAP documentation or guides related to the specific migration process you are using. This can provide insights into how to properly configure processing types.
- Testing: After making changes, perform a test run of the migration to ensure that the error has been resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
CNV789
Wrong routine type for aggregate routine &3 (field &2 of table &1)
What causes this issue? Aggregate routines must be of type 'F' (form routines). The routine &V3& provided for field &V2& of...
CNV780
Table &1 was not dropped; the update phase must not start
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV791
Potentially wrong duplicate processing type selected for table &1
What causes this issue? The table &V1& contains both key and non-key fields which are relevant for the conversion. In that case you should be...
CNV792
Too many fields of table &1 were marked with "Priority" indicator
What causes this issue? The "Priority" indicator may be assigned only to one field of the table &V1&.System Response The system is...
Click on this link to search all SAP messages.