How To Fix SCTS_DIST_CTL_COMAPI017 - TMS parameter NON_ABAP_WBO_CLIENT is not set correctly for system &1

SCTS_DIST_CTL_COMAPI017 - Overview

• Message type: E = Error

• Message class: SCTS_DIST_CTL_COMAPI - cCTS - All common API related Messages

• Message number: 017

• Message text: TMS parameter NON_ABAP_WBO_CLIENT is not set correctly for system &1

What causes this issue?

The parameter NON_ABAP_WBO_CLIENT is not set correctly for system &v1&.
This parameter specifies the logon client of the Transport Organizer in
the ABAP communication system of the non-ABAP system. It makes sure that
all transports are created in the correct client. It is used for
communication with the source system and is required for all non-ABAP
source systems. If you have performed the configuration steps for
non-ABAP transports, this parameter already exists in your source
systems.

How to fix this error?

Log on to the Transport Domain Controller of the communication system of
system &v1&.
Call transaction STMS.
Choose "System Overview".
Select the required system by double-clicking on it.
On the "Transport Tool" tab page, switch to change mode.
As required, add or change the TMS parameter "NON_ABAP_WBO_CLIENT" and
assign the correct value as described below.
Confirm the settings and distribute the TMS configuration.
INCLUDE CTS_EXPL_NON_ABAP_WBO_CLIENT OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

SCTS_DIST_CTL_COMAPI017 - Details

• The SAP error message SCTS_DIST_CTL_COMAPI017 indicates that the TMS (Transport Management System) parameter NON_ABAP_WBO_CLIENT is not set correctly for the specified system. This error typically arises in the context of transport management and can affect the ability to transport non-ABAP objects.
  
  Cause:
  The error occurs when the system is trying to perform a transport operation that involves non-ABAP objects, but the NON_ABAP_WBO_CLIENT parameter is either not set or is set incorrectly. This parameter is crucial for identifying the client that should be used for non-ABAP transports.
  
  Solution:
  To resolve this issue, you need to ensure that the NON_ABAP_WBO_CLIENT parameter is correctly configured in the Transport Management System. Here are the steps to do this:
  
  
  Access TMS Configuration:
  
  Go to transaction STMS in the SAP GUI.
  Click on the Transport Routes button.
  
  
  
  Check the Configuration:
  
  Select the system that is causing the error.
  Click on the Overview button and then select Systems.
  Choose the system in question and click on Change.
  
  
  
  Set the