Solution : https://service.sap.com/sap/support/notes/814707 (SAP Service marketplace login required)
Key words :
br>Data transfer results in corrupted characters.The trace files dev_wN and dev_rfcN contain error messages referring toFunctions starting with rscp* (see 'Other terms' below).Client side RFC terminates with error message "connection closed (no data)". Other terms Exception:SYSTEM_FAILUREShort dumps:RFC_CONVERSION_STRUCRFC_CONVERSION_TABLERFC_CONVERSION_FIELDCALL_FUNCTION_OPEN_ERRORError messages:"RFC connection to source system...is damaged ==> no metadata upload","Parameter ... cannot be converted from character set NNN to NNN", "codepage of receiver system cant determined. receiver destination was: nn"(B1 999),"The 0 line of the table could not be converted", or similar.rscpLangCPListGetCP rscpLangCPListGetCPtry rscpLangCPListGetCPdstrscpLCgetCtry readLClistA rscpLCgetC rscpLCgetCdst rscpConvertrscpLCListGetSize rscpLCListGetRSCP_RFCTRACE_SWITCH
Related Notes :
| 1319517 | Unicode Collection Note |
| 886571 | RFC non-Unicode ./. Unicode with illegal text language |
| 881781 | Unicode/non-Unicode RFC language and code page assignment |
| 871945 | Fallback Code Page for Zn Languages in Unicode/nonU RFC |
| 871468 | sm59: Error SCPRFC013 when maintaining MDMP code pages |
| 869322 | RFC Error with Language Z4 (internal key: ",") |
| 827999 | Error during transfer to MDMP tables with tRFC |
| 790485 | RFC Problem Single Code Page, non-Unicode to Unicode System |
| 722193 | RFC legacy non-Unicode clients and Unicode servers |
| 647495 | RFC for Unicode ./. non-Unicode Connections |
| 614550 | Troubleshooting BC-I18 |
| 548016 | Conversion to Unicode |
| 547444 | RFC Enhancement for Unicode ./. non-Unicode Connections |
| 480671 | The Text Language Flag of LANG Fields |
| 333441 |