CTS Communication Destinations 
All systems in a transport domain, as well as all systems of linked transport domains, are connected using RFC connections.
The following figure illustrates the RFC connections between all systems of a transport domain (development, quality assurance, and production systems) and also to a system that is linked to the transport domain.
The following destinations are relevant for CTS:
| Destination | User, Authorizations | Description |
|---|---|---|
| TMSADM@<SID>.<Transport Domain Name> |
User TMSADM in client 000 with profile S_A.TMSADM |
This RFC connection of type ABAP connection is
generated when TMS is configured. It is used for the following
purposes:
For more information, see RFC Connections in the TMS. |
| TMSSUP@<SID>.<Transport Domain Name> | Must not have a user configured | This RFC connection of type ABAP connection is
generated when TMS is configured. It is used to generate login prompts
for all actions for which TMSADM is not authorized. By default, the client is 000. |
| TMSWF@WORKFLOW_ENGINE |
User TMSADM_WF in configured client with profiles S_A.TMSADM and S_A.TMSWF |
This RFC connection of type ABAP connection is generated when
TMS Workflow is configured. It is used to generate transport proposals
in Business Workflow. For more information, see RFC Connections in the TMS. |
| CALLTP_<Operating_System_Type> <Operating_System_Type> = Windows, Linux , AIX, for example |
No user | This RFC connection of type TCP/IP connection
is generated dynamically at runtime. It is used to start the transport
control program tp. For more information on tp, see Transport Control Program tp. |