Kontakt

Ansicht
Dokumentation

OALE_RFCDEST_SM59 - Create RFC Connections

OALE_RFCDEST_SM59 - Create RFC Connections

TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

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
  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.

No RFC destinations are assigned in the standard system.

  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).

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.

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'

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.






ABAP Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3280 Date: 20240523 Time: 215950     sap01-206 ( 47 ms )