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

Diagnosis

The import destination to system is missing.

In order to distribute the CTS plug-ins, the import destination has to be configured in the CTS Server for every managed system.
For non-ABAP systems, the import destination must point to 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 a destination configured in SOLMAN_SETUP. You do not need to create a new import destination. Make sure that the Solution Manager destination is configured correctly. Afterwards, validate the system again.

Procedure

To create the import 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 Import Destination

  • "Destination Name": Enter the name according to the following naming convention: "TMSIMP@<SID>.<DOMAIN_NAME>".
  • "Technical Settings" tab:
    - For ABAP systems: Use the actual target system as the "Target Host" for the destination.
    - For non-ABAP systems: Use the communication system of the import target as the "Target Host" for the destination.
  • "Logon & Security" tab:
    We strongly recommend that you use Trusted system.
    - "User": Usually, you can leave the field empty.
    - "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.

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 "TMSIMP@ABC.DOMAIN_ABC".

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