SAP ABAP IMG Activity OALE_RFCDEST_SM59 (Create RFC Connections)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-MID-ALE (Application Component) ALE Integration Technology
     ⤷ SALC (Package) Application Link Enabling: Customizing
IMG Activity
ID OALE_RFCDEST_SM59 Create RFC Connections  
Transaction Code S_BCE_68000344   IMG Activity: OALE_RFCDEST_SM59 
Created on 19981207    
Customizing Attributes OALE_RFCDEST_SM59   RFC Destination for Asynchronous Processing 
Customizing Activity OALE_RFCDEST_SM59   RFC Destination for Asynchronous Processing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OALE_RFCDEST_SM59    

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

The Remote Function Call (RFC) 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
  • SAP connections
  • Internal connections
  • Logical destinations
  • CMC connections
  • SNA/CPI-C connections
  • TCP/IP connections
  • ABAP driver connections

Example

  1. For an SAP connection, enter the following parameters:
    • Name of RFC destination:    S11BSP001
    • Connection type:                3 (for SAP 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. Select one of the types (for example, SAP connections) and choose Edit -> create;
  2. Enter the parameters required for that type.
  3. For an SAP 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.

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OALE_RFCDEST_SM59 0 B200000069 RFC 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
SYSDUMMY D - Dummy object SM59 ALE07 RFC Destinations (Display/Maintain) 
History
Last changed by/on SAP  20021015 
SAP Release Created in