RFC and Unicode

The Remote Function Call (RFC) interface has also changed as part of the conversion to Unicode. The following remarks give a very brief outline of the general guidelines.

So that the RFC works in both USs and NUSs, an additional attribute has been added to the destination. This attribute specifies whether the RFC is to run in a US or a NUS. If an ABAP program uses function modules that change the RFC destination, this new attribute must be filled using another required parameter.

When text data is transferred in an RFC, the following new exceptions may occur:

A text cannot be converted from the source code page to the target code page because the corresponding character in the target code page is not available.
The field in the target system is shorter than the field in the source system. This may occur if data from a US is transferred to a multibyte system.
In principle, you can assume that text data has a different length in the sending system than in the receiving system. For this reason, we recommend that you use strings wherever possible. That is, you should try to avoid specifying the length of text data. You can, however, send binary data whose length is specified, without any problems.