How To Fix IUUC_MAIN118 - Table &1 refers to clone table &2 - should not be set to COMPLETE

SAP Error Message - Details

• Message type: E = Error

• Message class: IUUC_MAIN - IUUC: Main Message class

• Message number: 118

• Message text: Table &1 refers to clone table &2 - should not be set to COMPLETE

What causes this issue?

You changed to process option of a table to complete for which there is
an entry in table IUUC_PERF_OPTIONS which assigns a different table name
to this table. In such a case, this process option change might be
dangerous.

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 it is ok to transfer all table records of table &SYST-MSGV1& to
table &SYST-MSGV2&. Otherwise, remove the corresponding record from
table IUUC_PERF_OPTION. In case of any doubts, contact the SAP
backoffice.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message IUUC_MAIN118 - Table &1 refers to clone table &2 - should not be set to COMPLETE ?

  The SAP error message IUUC_MAIN118 indicates that there is an issue with the configuration of a table in the SAP Landscape Transformation (SLT) replication setup. Specifically, it points out that a table (denoted as &1) is referring to a clone table (denoted as &2), and the status of the clone table should not be set to "COMPLETE."
  
  Cause:
  This error typically arises in the context of SAP SLT when:
  
  A table that is being replicated has a clone table associated with it.
  The clone table's status is incorrectly set to "COMPLETE," which is not allowed in this scenario. The status should be set to "INITIAL" or "ACTIVE" depending on the replication state.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check the Status of the Clone Table:
  
  Use transaction code SLT or LTMOM to access the SLT configuration.
  Identify the clone table (the one referred to as &2 in the error message) and check its status.
  
  
  
  Change the