How To Fix CNV_DMC_SIN313 - Only one Lock Reason in same data record is allowed

CNV_DMC_SIN313 - Overview

• Message type: E = Error

• Message class: CNV_DMC_SIN - Messages for s-innovations migration

• Message number: 313

• Message text: Only one Lock Reason in same data record is allowed

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

It is not possible to set several lock reasons on same entry. Only one
lock reason is allowed. You can add several entries for creating more
lock reason for same Number of Contract Accts Rec. & Payable and Item
number in contract account document.
Further processing of the file is cancelled due to this several
combinations of lock reasons. The file will only be processed when there
is only one reason per entry.

How to fix this error?

Aggregate these entries to a unique combination with only one lock
reason per entry. You can add several entries to the subordinate sheet
Locking for BP Line Items with all needed lock reasons.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_DMC_SIN313 - Details

• The SAP error message CNV_DMC_SIN313 indicates that there is an issue with the data being processed in the Data Migration Cockpit (DMC) where only one lock reason is allowed in the same data record. This error typically arises during data migration activities, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools.
  
  Cause:
  The error occurs when the system detects multiple lock reasons assigned to a single data record. In the context of data migration, a lock reason is used to indicate why a particular record is locked or not available for processing. Having more than one lock reason for a single record violates the system's constraints, leading to this error.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Affected Records: Review the data records that are causing the error. You may need to check the logs or the error messages provided by the DMC to identify which