Supported Data and Transfer 

Data format

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).

Data Compression

Data is 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.

Data Conversion

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 SAP application server with transaction SM59.

Limitations of Data in one RFC Function

RFC library delivered with Release                          <  2.1K/2.2E            4 MB

>= 2.1K/2.2E          64 MB

>= 3.0                      none

Special Destinations in ABAP

·        Destination BACK:

During execution of an RFC function, you can use the destination BACK to call another RFC function in the client system 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.

·        Destination NONE for calls from SAP R/2 or SAP system:

In this case, the server system is the same SAP system as the client system.

¡        In the SAP system, it will be treated as a remote function call even if the RFC serveris the same application server (RFC data will be transferred via the SAP gateway).

¡        In R/2, however, it will be treated as a “local" CALL FUNCTION.

·        Destination SPACE