SAP ABAP Message Class SCTS_DIST_CTL_COMAPI Message Number 009 (Transport Organizer destination &2 to system &1 is missing)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CTS-TMS-CTR (Application Component) Central CTS # Transport Management
     ⤷ SCTS_DIST_CTL_COMMON_API (Package) cCTS: common external APIs
Attribute
Message class SCTS_DIST_CTL_COMAPI  
Short Description cCTS - All common API related Messages    
Message Number 009  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20140121   
Message Text
Transport Organizer destination &2 to system &1 is missing
Help Document

Diagnosis

The Transport Organizer destination to system is missing.

The Transport Organizer destination is required in the CTS server for every managed system of the cluster where transport requests are created.
For non-ABAP systems, the Transport Organizer destination has to be configured for the ABAP communication system of the selected non-ABAP system.
Note: If you are using Change Request Management (ChaRM) on top of central CTS, central CTS reuses the TMW destination. You do not need to create a new Transport Organizer destination. Make sure that the TMW destination is configured correctly. Afterwards, validate the system again.

Procedure

To create the Transport Organizer destination, proceed as follows:

  1. Call the RFC destination maintenance using transaction code SM59.
  2. Navigate to the ABAP connections and create a new "ABAP R/3 Connection (Type 3)".
  3. On the different tab pages, enter the data as described below.
  4. To create the destination, choose "Save".
  5. To make sure that the destination has been configured correctly, perform the connection test available in transaction SM59.
    Note: In order to perform the authorization test, the user that performs the test (logon user) must have the authorizations as described for the destination. Otherwise, the test can fail even though the destination was correctly configured.

Data for the Transport Organizer destination:

  • "Destination Name": Enter a name according to the following naming convention: "TMSORG@<SID><CLIENT>.<DOMAIN_NAME>"
  • "Technical Settings" tab: "Target Host":
    - For ABAP systems: Use the actual source system as the "Target Host" for the destination.
    - For non-ABAP systems: Use the communication system of the source system as the "Target Host" for the destination.
  • "Logon & Security tab":
    - "User": Use a specific user or single sign-on. We recommend that you configure Trusted systems. For test purposes, you may also use a specific user.
    - "Client": This is the client in which transport requests are created. For non-ABAP, the client in the destination must match the client configured for the non-ABAP source system (TMS parameter NON_ABAP_WBO_CLIENT).

Example: The non-ABAP system NAB is configured as the source system in client 001. It uses system ABC as communication system in domain DOMAIN_ABC. System ABC is also the CTS server and is used in client 100. In this case you must create a destination TMSORG@ABC001.DOMAIN_ABC.

History
Last changed on/by 20140121  SAP 
SAP Release Created in   702