REMOTE FUNCTION CALL:
The character conversion of the data to be transmitted is performed automatically.
Both single parameters and structures are supported for conversion.
The logon for remote SAP partner systems is automatic. The user and password are stored in the table RFCDES.
RFC calls in C are available for communicating with external programs (RFC-SDK). The RFC Generator also helps you when generating RFC programs in C.
If a function module is called remotely, it runs in its own work process (its own SAP LUW) if the remote system is an R/3 System.
The remote destination can be another application server in the same or a different R/3 System, an When you call a function module locally, it runs in the same work process as the calling program.
R/2 System, or an non-SAP system.
Note that the calling program is rolled out for each remote function call, which triggers an implicit database-commit.
You maintain RFC destinations that must specify an ABAP program when calling remote function modules in the RFC sideinfo table RFCDES using Transaction SM59.
For each partner system, you need to maintain one entry in the sideinfo table.
SAP delivers the RFC Library for all current external platforms, in which RFC calls are contained for C programs. After installing the RFC Library on your external platform, you can implement RFC client or RFC server programs using RFC calls.
With synchronous RFC, processing stops in the calling program until the called remote function is processed and its output is returned. Then in the calling program, the processing continues after the call.
In an asynchronous Remote Function Call, the called remote function is started and then continues processing on its own immediately in the calling program. Remote function processing is separate from the calling program. The function output can be received later in the program.
Asynchronous RFC is intended for parallel processing of processes.
Whereas with synchronous and asynchronous RFC each call makes up a single logical unit of work (LUW) in the remote system, you can use transactional RFC to bundle several remote functions into one LUW (with an automatic rollback mechanism in case of error).
With tRFC, generated LUWs are processed independently of each other. This means, the order in which they are processed is not always the order in which they are generated.
To ensure that tRFC-LUWs are processed in the same order as they were generated, you can use qRFC as an extension of tRFC.
qRFC is available as of Release 4.6A and can be used in R/3-R/3 connections as well as R/3-external connections.
RELATED POSTS
RFC PART 2
The character conversion of the data to be transmitted is performed automatically.
Both single parameters and structures are supported for conversion.
The logon for remote SAP partner systems is automatic. The user and password are stored in the table RFCDES.
RFC calls in C are available for communicating with external programs (RFC-SDK). The RFC Generator also helps you when generating RFC programs in C.
If a function module is called remotely, it runs in its own work process (its own SAP LUW) if the remote system is an R/3 System.
The remote destination can be another application server in the same or a different R/3 System, an When you call a function module locally, it runs in the same work process as the calling program.
R/2 System, or an non-SAP system.
Note that the calling program is rolled out for each remote function call, which triggers an implicit database-commit.
You maintain RFC destinations that must specify an ABAP program when calling remote function modules in the RFC sideinfo table RFCDES using Transaction SM59.
For each partner system, you need to maintain one entry in the sideinfo table.
SAP delivers the RFC Library for all current external platforms, in which RFC calls are contained for C programs. After installing the RFC Library on your external platform, you can implement RFC client or RFC server programs using RFC calls.
With synchronous RFC, processing stops in the calling program until the called remote function is processed and its output is returned. Then in the calling program, the processing continues after the call.
In an asynchronous Remote Function Call, the called remote function is started and then continues processing on its own immediately in the calling program. Remote function processing is separate from the calling program. The function output can be received later in the program.
Asynchronous RFC is intended for parallel processing of processes.
Whereas with synchronous and asynchronous RFC each call makes up a single logical unit of work (LUW) in the remote system, you can use transactional RFC to bundle several remote functions into one LUW (with an automatic rollback mechanism in case of error).
With tRFC, generated LUWs are processed independently of each other. This means, the order in which they are processed is not always the order in which they are generated.
To ensure that tRFC-LUWs are processed in the same order as they were generated, you can use qRFC as an extension of tRFC.
qRFC is available as of Release 4.6A and can be used in R/3-R/3 connections as well as R/3-external connections.
RELATED POSTS
RFC PART 2
No comments :
Post a Comment