Which error messages may occur if there are problems with RFC data transfer between Unicode and non-Unicode systems?
A short dump, exception or error message may occur as mentioned below:
"RFC connection to source system...is damaged ==> no metadata upload",
"Parameter ... cannot be converted from character set NNN to NNN", "codepage of receiver system cannot be determined. Receiver destination was: nn"(B1 999),
"The 0 line of the table could not be converted", or similar.
rscpLangCPListGetCP rscpLangCPListGetCPtry rscpLangCPListGetCPdst
rscpLCgetCtry readLClistA rscpLCgetC rscpLCgetCdst rscpConvert
It is also seen that Data transfer results in corrupted characters.
The trace files dev_wN and dev_rfcN contain error messages referring to
Functions starting with rscp* (see 'Other terms' below)
Client side RFC terminates with error message "connection closed (no data)".
For Unicode/non-Unicode RFC connections, a code page conversion is performed for language dependent data on the Unicode system
Problems usually arise when:
• No code page or an improper code page is allocated to language keys in data
• Language keys in data are corrupt or illegal
• Data are not convertible between Unicode and non-Unicode code page
How can I get this resolved?