SAP ABAP Message Class SCTS_DIST_CTL_COMAPI Message Number 011 (Deploy 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 011  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20140121   
Message Text
Deploy destination &2 to system &1 is missing
Help Document

Diagnosis

The deploy destination to system is missing.

The deploy destination is required in the CTS Server for every managed target system into which transport requests are to be imported that belong to transport collections.
For non-ABAP systems, the deploy destination must point to the ABAP communication system of the selected non-ABAP system.

Procedure

To create the deploy 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.

Prerequisites for the Deploy Destination

You need a technical user with specific authorizations in the managed system that is used for communication between the CTS server and the managed system. You must create this user in the managed system. For non-ABAP systems, you must create it in the communication system of the managed system. To do so, proceed as follows:

  1. Log on to the managed system for which you need the Deploy destination in any client.
  2. Create a technical user of type "System" (sample user name CCTSTRANS):

    Assign the following roles to this user:
    • A copy of the role SAP_BC_TRANSPORT_OPERATOR.
    • A new role that you create yourself (sample role name Z_TRANS_RFC_ACL):

      The new role must contain the authorization object S_RFCACL with the following fields and values:

      - "Activity" (ACTVT): "Execute (16)"
      - "RFC client or domain" (RFC_CLIENT): "000" (required for import process)
      - "RFC same user ID" (RFC_EQUSER): "Call by the same user is not possible (No)"
      - "RFC information" (RFC_INFO): "*"
      - "System ID (for SAP and External)" (RFC_SYSID):"<communication system of the cluster>"
      - "RFC transaction code" (RFC_TCODE): "*"
      - "RFC User (SAP or External)" (RFC_USER): "DDIC"

      For more information, see "Authorization Object S_RFCACL" on SAP Help Portal.

Data for Deploy Destination

  • "Destination Name": Enter the name according to the following naming convention: "TMSDPL@<SID>.<DOMAIN_NAME>"
  • "Technical Settings" tab:
    - For ABAP systems: Use the actual managed system as the "Target Host" for the destination.
    - For non-ABAP systems: Use the communication system of the managed system as the "Target Host" for the destination.
  • "Logon & Security" tab:
    We strongly recommend that you use Trusted system with the technical user described in the "Prerequisites" section.
    - "Language": Enter a language that is installed both in the CTS Server and in the managed system. We recommend that you use English (EN).
    - "Client": Enter the client of the managed system in which you have created the technical user.
    - "User": Enter the technical user that you created in the managed system.
    - "Trust Relationship": Select "Yes".
    In addition, to encrypt communication data, we recommend that you use Secure Network Connection (SNC) for RFC communication with managed target systems.
    With this setup, you make sure that only user DDIC in client 000 is allowed to communicate using the deploy destination.

Example: The non-ABAP system NAT is configured as the target system and uses system ABC as the communication system in domain DOMAIN_ABC. System ABC is also the CTS server. In this case you must create a destination "TMSDPL@ABC.DOMAIN_ABC".

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