How To Fix CNV_PE_CHECK347 - Link type 'Copy' is maintained for field &1

CNV_PE_CHECK347 - Overview

• Message type: E = Error

• Message class: CNV_PE_CHECK - Check Framework messages for posting engine

• Message number: 347

• Message text: Link type 'Copy' is maintained for field &1

What causes this issue?

Data field &V1& has one of the following field transformations:
Transformation type is <ZK>Transformation Rule</>
Transformation type is <ZK>Relevance Ident Specific</> and
transformation type of at least one of the relevance identifiers is <ZK>
Transformation Rule</>.
In transfer method -> <ZK>Transformation</> tab -> <ZK>Knowledge Base</>
-> <ZK>Scenario Independent</> the link field &V2& is assigned to the
data field with a link type <ZK>Copy</>. In this case, the provided
transformation rule will be called twice with the same input data: once
for the data field &V1&, the other time - for link field &V2&. The
returned values will <ZH>not</> be compared afterwards.

System Response

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

How to fix this error?

Check if the provided transformation rule returns the same value when
called twice in succession.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_PE_CHECK347 - Details

• The SAP error message CNV_PE_CHECK347 indicates that there is an issue with the link type 'Copy' being maintained for a specific field in a conversion project, typically related to data migration or transformation processes. This error is often encountered during the execution of a data migration project using the SAP Data Migration Workbench or similar tools.
  
  Cause:
  The error occurs when the system detects that a field is set to use the 'Copy' link type, which may not be appropriate for the specific context or data transformation being performed. This can happen due to:
  
  Inconsistent Data Mapping: The field may not be correctly mapped to the target structure, leading to conflicts in how data should be handled.
  Business Logic Violations: The business rules defined for the data migration may not allow for a direct copy of the data from the source to the target.
  
  Configuration Issues: There may be configuration settings in the migration project