Trigger missing for table &1 (mass transfer ID &2); replication suspended

What causes this issue?

When SAP Landscape Transformation Replication Server replicates a table
to the target system, it creates a database trigger in the source system
that records any changes in a logging table. For the table listed above,
this trigger is missing.
This can happen for one of the following reasons:
The trigger was deleted manually using database administration tools.
The trigger was deleted manually using one of the expert functions
provided by SAP Landscape Transformation Replication Server.
The structure of the table was changed, for example during an upgrade.
Note that you can use expert function View Trigger Source Code in the
SAP LT Replication Server Cockpit (transaction LTRC) to determine
whether the trigger is really missing.

System Response

Since the database trigger is needed to record any changes to the source
system table, some changes to the source table might have been lost (and
not replicated to the target system). The system suspends the
replication of the table, sets the status of the table status to Failed,
and the sets the status of the trigger Inconsistent.

How to fix this error?

We recommend that you stop the replication of the table, and restart the
replication process. This ensures that the source and target tables are
synchronized.
If you are absolutely sure that the source table was not changed since
the trigger was identified as missing, you can reset the status of the
trigger. You can do this in the SAP LT Replication Server Cockpit
(transaction LTRC) by using the expert function Reset Status for Trigger
and Logging Tables. You can then recreate the trigger manually by using
the processing step Create Database Triggers.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.