How To Fix CNV_DMC_WDA128 - Field æ&1Æ is not displayed under æData RecordsÆ; see long text

CNV_DMC_WDA128 - Overview

• Message type: E = Error

• Message class: CNV_DMC_WDA - Messages used in WDA UI

• Message number: 128

• Message text: Field æ&1Æ is not displayed under æData RecordsÆ; see long text

What causes this issue?

In the SAP HANA Studio, you have added a field to the staging table.
However, the field name is not supported by the SAP S/4HANA migration
cockpit. The column for the field is therefore not displayed under ?Data
Records?.

System Response

How to fix this error?

The structure of the staging table must be adjusted so that it reflects
the latest version of the migration object. This means the field must be
removed from the staging table.

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

Note: Before you start the procedure below, ensure that the field is not
required and can be removed.
To do this, choose the button Start Synchronization. The system will
remove the field that was added to the staging table.
Alternatively, you can remove the field from the staging table directly
in the SAP HANA Studio. You can then add a field with a valid format, if
required.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_DMC_WDA128 - Details

• The SAP error message CNV_DMC_WDA128 typically occurs during data migration processes, particularly when using the SAP Data Migration Cockpit (DMC) or similar tools. This error indicates that a specific field (represented by &1 in the message) is not displayed under the "Data Records" section, which can hinder the data migration process.
  
  Cause:
  
  Field Configuration: The field in question may not be configured correctly in the source or target system. This could be due to missing field mappings or incorrect data types.
  Data Structure Changes: If there have been changes in the data structure (e.g., fields added or removed) between the source and target systems, the migration tool may not recognize the field.
  Authorization Issues: The user executing the migration may not have the necessary authorizations to view or manipulate the specified field.
  Technical Issues: There could be underlying technical issues, such as bugs in the migration tool or inconsistencies in the data model.
  
  
  Solution:
  
  Check Field Configuration: