Show TOC

Creating a Type 3 RFC Destination on SAP NetWeaver Gateway Host to SAP SystemLocate this document in the navigation structure

Use

A Type 3 connection from the SAP NetWeaver Gateway host to the SAP Business Suite system is required for all scenarios. Create this as follows

  1. In transaction SPRO open the SAP Reference IMG and navigate to: Start of the navigation path SAP NetWeaver Next navigation step Gateway Next navigation step OData Channel Next navigation step Configuration Next navigation step Connection Settings Next navigation step SAP NetWeaver Gateway to SAP System Next navigation step Manage RFC Destinations End of the navigation path and click on the Activity icon.

  2. Choose Create.

  3. In the RFC Destination field, enter the RFC destination name in the following format: <system id >CLNT<Client>.

  4. In the Connection Type field, enter 3.

  5. In the Description 1 field, enter an explanatory text, for example, RFC Destination to SAP Server.

  6. Save your settings.

  7. On tab Technical Settings and Load Balancing select the relevant option according to your system's settings.

  8. In the Target Host field, enter the (message) server name of the of the SAP system.

  9. In the System Number field, enter the SAP NetWeaver Gateway system number, for example, 00.

  10. On tab Logon & Security enter the SAP system's client number.

  11. Activate Current User.

  12. For Trust Relationship activate Yes.

    Note

    Ensure that you have previously created the trusted relationship, as outlined in Defining Trust between the SAP NetWeaver Gateway Host and Your SAP System.

  13. Save your settings.

  

To check that you have successfully created the type 3 connection, choose Connection Test. The connect test should pass.

If the user ID with which you are logged on to SAP NetWeaver Gateway and your user ID for the SAP system is the same, and this user ID has the object S_RFCACL assigned to it on the SAP system, select Remote Logon. You should not see any error messages in the status. If you have any problems, check SAP Note 128447 Information published on SAP site for troubleshooting tips.