Show TOC

Background documentationTMS Parameters for Central CTS Locate this document in the navigation structure

 

The following TMS parameters are required to work with central CTS.

MANAGED_SYSTEM

This parameter classifies the system as managed.

The following values are available:

Value

Description

TRUE

The system is managed by central CTS.

PARTLY

The system is managed partially by central CTS.

You can control imports both using the central CTS server and using the local Transport Management System. Transport requests that were created using central CTS are controlled by central CTS. Transport requests that were created locally in the SAP system can be imported using the local Transport Management System.

You can use this value if you want to introduce central CTS step-by-step or for test purposes.

OPERATION_MODE

This parameter specifies the operating mode of the system. It defines the extent of import control that the central CTS has for the managed systems.

It must always be set in connection with the TMS parameter MANAGED_SYSTEM.

The following values are available:

Note Note

The following description of the parameters is valid for all transport requests that were created using central CTS if the TMS parameter MANAGED_SYSTEM is set to TRUE or PARTLY. However, it does not apply to transport requests that were created locally in the system if MANAGED_SYSTEM is set to PARTLY.

End of the note.

Value

Description

CONTROLLED

The central CTS server controls the transports in the managed systems. Imports can no longer be executed locally in the managed systems.

CONTROLLED_DYNAMIC

The central CTS server controls transports dynamically in the managed systems. Imports can no longer be executed locally in the managed systems.

Another program on top of central CTS, such as Change Request Management (ChaRM), defines the level of control for the managed systems.

PROPOSED

The central CTS server suggests imports for the managed systems by placing transports in the import queue. Imports must be started locally in the system.

PROPOSED_DYNAMIC

The central CTS server suggests imports for the managed systems by placing transports in the import queue. Imports must be started locally in the system.

Another program on top of central CTS, such as Change Request Management (ChaRM), defines the level of control for the managed systems.

MONITORED

The central CTS server only has a monitoring function. Transports must be started locally in the systems.

NON_ABAP_WBO_CLIENT

This parameter specifies the logon client of Transport Organizer. It is used for communication with the source system. It is required for all non-ABAP source systems and for system clusters. If you have performed the configuration steps for non-ABAP transports, this parameter already exists in your source systems.

Note Note

You can only set this parameter in TMS, not in the Central CTS Configuration Web UI.

End of the note.

The following values are available:

Value

Description

000-999

Value of the logon client in Transport Organizer. This is the client in which your TMS was configured and in which you are developing.