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:
No RFC destinations are assigned in the standard system.
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.
The 'SAP*' user cannot be used for remote function calls on the target system.
For connecting to R/2 Systems:
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/，如需转载，请注明出处，否则将追究法律责任。