on 06-29-2007 1:11 PM
hi all,
what are the different types of RFCs and difference between them(RFC,TRFC etc)
Regards
raj
Dear Raj,
what are the different types of RFCs and difference between them(RFC,TRFC etc)
The RFC Interface
RFC in SAP Systems
RFC is an extension of CALL FUNCTION in a distributed environment. Existing function modules can be executed from within a remote system (R/2 or R/3) via an RFC call. Adding a DESTINATION clause to the CALL FUNCTION statement does this:
The destination parameter displays an entry in the RFCDES table (which is defined with transaction SM59). This entry contains all necessary parameters to connect to and log in the destination system. The RFC API on OS/2, Windows, Windows NT and all R/3-based UNIX platforms makes it possible to use the RFC functionality between an SAP System (R/3 from Release 2.1 and R/2 from Release 5.0D onwards) and a C program on the above platforms. It is of no significance to the caller whether the remote function is provided in an SAP System or in a C program. RFC frees the ABAP programmer from having to program his own communications routines. When you make an RFC call, the RFC interface takes care of:
· Converting all parameter data to the representation needed in the remote system. This includes character string conversions, and any hardware-dependent conversions needed (for example, integer, floating point). All ABAP data types are supported.
· There is no support for Dictionary structures.
· Calling the communication routines needed to talk to the remote system.
· Handling communications errors, and notifying the caller, if desired. (The caller requests notification using the EXCEPTIONS parameter of the CALL FUNCTION statement.)
The RFC interface is effectively invisible to the ABAP programmer. Processing for calling remote programs is built into the CALL FUNCTION statement. Processing for being called is generated automatically (in the form of an RFC stub) for every function module registered as remote. This stub serves as an interface between the calling program and the function module.
A distinction is made between an RFC client and RFC server. RFC client is the instance that calls up the Remote Function Call to execute the function that is provided by an RFC server. In the following, the functions that can be executed remotely will be called RFC functions and the functions provided via RFC API will be called RFC calls.
All RFC functions available in a remote RFC server system, which are called by an RFC client, are processed transactionally. This means that after execution of the first RFC function in the RFC server system the complete context (all globally defined variables in the RFC server program or in the main program of a function module) is available for further RFC functions. The RFC connection is closed only
· When the context of the calling ABAP program has ended or
· Explicitly by RfcAbort or RfcClose in the external program.
Until Release 3.0 the connection to an R/3 System must be established to a previously defined application server. From Release 3.0 onwards, it is also possible to have an application server assigned by the message server on the basis of a load balancing procedure. This applies both for RFC between R/3 systems and between external systems and R/3 systems.
To make the execution of RFC functions reliable, safe and independent from the availability of the RFC server or RFC server system, the transactional RFC (tRFC) was introduced for R/3 systems from Release 3.0 onwards. This ensures that the called function module is executed only once in the RFC server system. In transactional RFC calls, the data that belongs to an RFC function must first be stored temporarily on the SAP database in the RFC client system. When processing is completed, this must be reported back to the calling ABAP program. Everything else is handled by the tRFC component in the R/3 System. Since a database is not always available on external systems, the link to the tRFC interfaces is implemented such that the client or server programs based on RFC API must take on some administrative functions to ensure that the respective function module is executed "only once".
Best Regards,
Srikanth
Reward the useful answers and you will get one point yourself<a href="https://answers.sap.com/people/baris.buyuktanir2/blog/2007/04/04/point-for-points-reward-yourselfyourself
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Raj
<i>different types of RFCs</i>
There are 5 types of RFCs
1. Synchronous RFC (sRFC) - calll waits for target response n then only the control proceeds
2. Asynchronous RFC (aRFC) - can be with or without response - "With" action like emailing based on any condition "Without" - exception raised during execution of RFM not propogated to client.
3. Transactional RFC (tRFC) - let us group one or more function modules - all FM are executed or none. Used for guaranteed transactional execution
4. Queued RFC (qRFC) - To conrol the execution order
5. Parallel RFC (pRFC) - Extension of aRFC. We can select group of Application servers to execute the RFCs. Multiple RFC destinations, Built-in load balancing and alerting mechanism
<i>difference between them(RFC,TRFC etc)</i>
All messges in XI are processed in Queues. These Queues can be TRFC's ( Transactional RFC's ) or QRFC ( Queue RFC's ).
this has nothing to do with the RFC's created in SE37 on your R3 system.
Refer the following help doc
http://help.sap.com/saphelp_nw04/helpdata/en/8b/ceea3b31aac554e10000000a114084/content.htm
Cheers..
Vasu
<i>** REward Points if found useful **</i>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
check this
http://help.sap.com/saphelp_nw70/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/frameset.htm
regards
krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.