Supported Data and Transfer
Only homogenous structures or tables are supported. They must consist of character fields only (ABAP-types C, D, T, N) or fields which will not be converted (ABAP-types X or P). Integer (ABAP-type I) or float (ABAP-type F) fields can only be transfered as single fields (IMPORT/EXPORT parameters).
From R/3 Release 3.0 onwards, RFC data will be compressed before sending, if both client and server system are capable of this. Otherwise, only the blank spaces at the end of a table line will be truncated.
The SAP System or the RFC library will convert received data in its own code page if the two code pages are not the same.
Some standard code pages (such as 1100, 0100, etc.) are already implemented in the RFC library. It can also use a conversion file defined by the environment variable PATH_TO_CODEPAGE. The files can be created and downloaded into a directory accessible from the currently running R/3 application server with transaction SM59.
Limitations of Data in one RFC Function
RFC library delivered with R/3 Release < 2.1K/2.2E 4 MB
>= 2.1K/2.2E 64 MB
>= 3.0 none
Special Destinations in ABAP (R/3 or R/2)
During execution of an RFC function, you can use the destination BACK to call another RFC function in the client system (SAP R/2 or R/3) or in the RFC client program (external program via RFC API) using the same RFC connection.
This destination is not available in R/2 Systems.
In this case, the server system is the same SAP System (R/2 or R/3) as the client system.
This destination is only possible as of R/3 Release 3.0.
This destination is treated like a "local" CALL FUNCTION.