Create RFC Connections

Create RFC Connections

In this section, you define the technical parameters for the RFC destinations.

The Remote Function Call is controlled by the RFC destination parameters.

To create an RFC port, the RFC destinations must be assigned.

The name of the RFC destination should be the same as the logical system name.

The following types of RFC destinations can be assigned:

• R/2 connections

• R/3 connections

• Internal connections

• Logical destinations

• CMC connections

• SNA/CPI-C connections

• TCP/IP connections

• ABAP driver connections

Example

1. 1. For an R/3 connection, enter the following parameters:

• • Name of RFC destination: S11BSP001

• • Connection type: 3 (for R/3 connection)

• • Target system: bspserver01

• • System number: ,11

• • User in target system: CPIC

• • Password, language and target client.

Standard settings

No RFC destinations are assigned in the standard system.

Activities

1. 1. Select one of the types (for example, R/3 connections) and choose

Edit -> create;

1. 2. Enter the parameters required for that type.

1. 3. For an R/3 connection, these are, for example, the name of the RFC destination, the name of the partner system, logon parameters (see example).

Processing RFCs With Errors

Since RFC destinations are usually registered in the QOUT Scheduler when you use ALE, it is usually no longer necessary to schedule the program RSARFCEX in a background job for the collective processing of RFCs with errors. We also recommend that you do not do this. The QOUT Scheduler now repeats the execution of RFCs with errors automatically (See transaction SMQ1. For detailed documentation about the QOUT Scheduler, see the SAP Library under qRFC (Queued Remote Function Call)).

In some cases, for example, if there are many RFCs with errors, and they cannot be executed again with the QOUT Scheduler, you can start the report RSARFCEX manually.

Practise handling errors in remote function calls before the function is used productively.

Further notes

The 'SAP*' user cannot be used for remote function calls on the target system.

For connecting to R/2 Systems:

• Use an R/2 destination to read the users with passwords. The actual communication uses CPI-C.

• Select 'Unencrypted password'

Notes on the transport

The maintenance of the RFC destination is not a part of the automatic Change and Transport System. Therefore the setting has to be made manually on all systems.

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/7941665/viewspace-970842/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/7941665/viewspace-970842/