Message type: E = Error
Message class: CNV - Conversion: Messages for Conversion Services (CNCC)
Message number: 360
Message text: Conflict occurs during priority handling of the record
During the conversion of the record, it comes to a merge in the
database. That means, there are two records with the same primary key
values and one of them should be deleted. In order to decide which
record should be deleted, there are defined at least two priority
routines . The priority routines provide different results in regard to
this.
No priority will be used for the record. Namely, the record will be
deleted from the database.
Check the original values of the record in log and the related messages
to see the results of each priority routine. Contact SAP for support in
case that errors occur related to this bevaviour.
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 "CNV360 Conflict occurs during priority handling of the record" typically arises in the context of data migration or conversion processes, particularly when using SAP's Conversion Tools or during the execution of a data migration project. This error indicates that there is a conflict in the priority handling of records being processed, which can occur for various reasons.
Causes:
- Duplicate Records: The error may occur if there are duplicate records in the source data that are being processed, leading to conflicts in how priorities are assigned.
- Inconsistent Data: If the data being migrated has inconsistencies or conflicts in key fields that are used to determine priority, this can trigger the error.
- Incorrect Configuration: Misconfiguration in the migration tool settings or parameters can lead to conflicts in record handling.
- Data Dependencies: If there are dependencies between records that are not being respected, it can lead to conflicts during processing.
Solutions:
- Check for Duplicates: Review the source data for duplicate records and resolve any duplicates before running the migration process again.
- Data Cleansing: Ensure that the data is clean and consistent. This may involve standardizing formats, correcting errors, and ensuring that all required fields are populated correctly.
- Review Configuration: Check the configuration settings of the migration tool to ensure that they are set up correctly. This includes reviewing priority settings and any rules that govern how records are processed.
- Analyze Dependencies: If there are dependencies between records, ensure that they are handled correctly in the migration process. This may involve adjusting the order of processing or ensuring that related records are processed together.
- Consult Documentation: Refer to SAP documentation or notes related to the specific migration tool you are using for any known issues or additional troubleshooting steps.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.
Sign up takes 1 minute. 7-day free trial.
CNV345 Non-transparent parameter &1 for field &2, table &3 not defined correctly
What causes this issue? The given non-transparent parameter is not defined corr...
CNV344 Conflicting non-transparent fields of table &1
What causes this issue? Table &V1& contains conflicting non-transparent...
CNV361 Priority routine: '&1', Priority value: '&2'
What causes this issue? The different priority routines and their respective va...
CNV400 ****** 400 - 444 reserved for user lock and IMG *******
Self-Explanatory Message Since SAP believes that this specific error message is ...
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.