How To Fix CNV_DMC_HC069 - &1 - &2: Logging table &3 does not exist in the source system

CNV_DMC_HC069 - Overview

• Message type: E = Error

• Message class: CNV_DMC_HC -

• Message number: 069

• Message text: &1 - &2: Logging table &3 does not exist in the source system

What causes this issue?

The logging table does not exist in the source system.

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?

In transaction LTRC, you can view the possible causes of the issue. On
the tabs <ZK>Table Overview</> and <ZK>Data Transfer Monitor</>, you can
choose the <ZK>View Errors</> pushbutton. On the tab <ZK>Application
Logs</>, you can also view the logs for the initial load and for the
replication process.
The error messages and logs can provide guidance for resolving the
issue, for example you can:
Create the logging table manually by using the step <ZK>Create Logging
Tables</> (in transaction LTRC on the tab <ZK>Processing Steps</>)
Stop and start the table again.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CNV_DMC_HC069 - Details

• The SAP error message CNV_DMC_HC069 indicates that a logging table specified in the data migration process does not exist in the source system. This error typically arises during data migration activities, particularly when using the SAP Data Migration Cockpit or similar tools.
  
  Cause:
  
  
  Missing Logging Table: The logging table referenced in the error message is not present in the source system. This could be due to:
  
  The table was never created.
  The table was deleted or dropped.
  The migration process is incorrectly configured to reference a non-existent table.
  
  
  
  Incorrect Configuration: The migration configuration might be pointing to the wrong source system or schema where the logging table is expected to exist.
  
  
  Version Mismatch: There may be a version mismatch between the source and target systems, leading to differences in the expected database schema.
  
  
  
  Solution:
  
  
  Verify Table Existence: Check the source system to confirm whether the logging table (&3 in the error message) exists. You can do this by executing