Академический Документы
Профессиональный Документы
Культура Документы
co m
EXPORTING f1 =<br>
IMPORTING f2 =<br>
TABLES t 1 =<br>
EXCEPTIONS
Logical Destinations are def ined via transaction SM59 and stored in Table RFCDES
Functions of the RFC interface
Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notif ying the caller, if desired ( using EXCEPT IONS paramater
of the CALL FUNCT ION).
Types of RFC
1. Synchronous RFC - T he calling program continues the execution only af ter the called f unction is
complete.
2. Asynchronous RFC - T he calling program continues the execution without waiting f or return f rom
the called f unction.
3. Transactional RFC - T he called f unction module is executed exactly once in the RFC target
system.Each f unction call is seen as a transaction in the target system. Transactional RFCs use the
suf f ix IN BACKGROUND TASK . Eg : CALL FUNCT ION 'remotef unction' IN BACKGROUND TASK
3.Def ine the destination of the RFC server in the RFC client system that calls the remote f unction ( via
SM59 transaction).
4.Declaring Parameters: All parameter f ields f or a remote f unction module must be def ined as ref erence
f ields, that is, like ABAP Dictionary f ields.
5.Exceptions: T he system raises COMMUNICAT ION_FAILURE and SYST EM_FAILURE internally. You can
raise exceptions in a remote f unction just as you would in a locally called f unction.