RFC - Remote Function Call in Release 4.0
Asynchronous RFC
ABAP_MODIFICATION_1 WAIT [UNTIL
condition] UP TO time SECONDS
The WAIT command allows you to wait for a response from a
function module called asynchronously. This requires the addition
PERFORMING form ON END OF TASK . WAIT must occur in the same
program context (session).
ABAP_MODIFICATION_2 RECEIVE RESULTS FROM FUNCTION func
KEEPING TASK
The KEEPING TASK addition preserves the remote context in the
subroutine for reuse.
Other Changes
ABAP_MODIFICATION_3 Error messages from the remote system
If an error occurs in the target system in RFC, details of the
error message are passed to the calling
system (SY-MSGNO, SY-MSGID, SY-MSGTY, SY-MSGV1, SY-MSGV2, SY-MSGV3
, and SY-MSGV4 ). These fields are set to initial in each RFC
call.
ABAP_MODIFICATION_4 Load checks for asynchronous RFC
For each RFC destination , an improved
load check is performed for asynchronous RFCs (menu path Destination
- ARFC Options in the RFC destination maintenance screen in
AS ABAP . Before the function
module is executed, the system makes sure that the target host has
enough resources. If the host is overloaded, the execution of the
function module is delayed (internally) for a short time. The algorithm
used to determine the host's load is the same used in asynchronous RFC
with the addition DESTINATION IN
GROUP . Be aware that this option can only be used for target
hosts from Release 3.1H .
ABAP_MODIFICATION_5 SNC option maintenance for RFC
destinations
You can define security options for each RFC destination. This is also
possible for RFC Secure Network Communication . The SNC
component ( Secure Network Communications ) provides added
protection, for example by encrypting data transfers and applying secure
mutual authorization between communication partners.
To use SNC , you must already have an external security product
installed and entered in your profile (see, for example, parameter
snc/enable ). If you are using SNC , you can choose whether or
not you want to use your additional protection functions for this
destination in the SNC Mode setting. If this is the case, you
must define additional SNC options using the menu bar:
Destination - SNC Options .
ABAP_MODIFICATION_6 RFC clients as trusted systems
An RFC client that is registered as a trusted system can log on to the
RFC server without a password. Trusted systems must be defined in the
trusting system (the RFC server) using the transaction
SMT1 . In the trusted system, you can use the transaction code
SMT2 to determine which systems act as trusting
systems.
ABAP_MODIFICATION_7 Authorization check
If RFC communication takes place within a single system and in the same
user context (with the same client and user ID), then no RFC
authorization check based on function groups (using the
authorization object S_RFC
) is performed. For more information, see RFC
Authorization Concept .
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved