How To Fix SCWN118 - This manual activity is not transportable

SCWN118 - Overview

• Message type: E = Error

• Message class: SCWN - Messages Note installation and management

• Message number: 118

• Message text: This manual activity is not transportable

What causes this issue?

When the request is transported to the follow-on systems, the manual
activity is not transported.

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?

If the manual activity is a manual pre-implementation step, you need to
perform this in the follow-on systems before importing the request into
the follow-on systems.
If the manual activity is a manual post-implementation step, you need to
perform this in the follow-on systems after importing the request into
the follow-on systems.
Then call Note Assistant in the follow-on systems and start implementing
the note again, in order to confirm that the manual activities have been
performed. In the follow-on systems, the note then has the status
'completely implemented'.

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 SCWN118 - This manual activity is not transportable ?

  The SAP error message SCWN118, which states "This manual activity is not transportable," typically occurs in the context of SAP Change and Transport System (CTS) when you are trying to transport a manual activity that is not allowed to be transported between systems.
  
  Cause:
  The error arises because certain manual activities, such as configuration changes or specific settings made directly in the system, are not designed to be transported. This is often the case with:
  
  Manual entries in customizing (transaction SPRO).
  Changes made directly in the database that are not recorded in a transport request.
  Activities that are specific to a particular client or system and cannot be replicated in another environment.
  
  
  Solution:
  To resolve this issue, you can consider the following approaches:
  
  
  Identify the Manual Activity: Determine which specific manual activity is causing the error. This can often be found in the transport logs or by reviewing the changes made.
  
  
  Document the Changes: Since the manual activity cannot