The result string that your WebRFC must return is as I posted above. Your result is exactly the same as it was before (no change) so of course it will fail.
You have to incorporate logic in your WebRFC based on the DEMO_ESCAPE program which encodes any special characters. The proper encoding for æ is \u00E6 - I tested this to work fine with a WebRFC so I know it is correct.
![Capture.JPG]()
Edit: Upon further investigation, it appears that the escape function doesn't work for JSON like the documentation would imply. So here is some quick Mickey Mouse code to perform the encoding. Never mind the not exactly sophisticated exception handling; hopefully this won't be necessary anyway.
txt_in is the original text, result is the encoded string to be returned by the WebRFC.
DATA: txt_in TYPE string VALUE 'Dampfærgevej+17,2100',
chr TYPE char1,
strlength TYPE i,
offset TYPE i,
icode TYPE i,
hcode TYPE syhex02,
ccode TYPE char4,
result TYPE string,
gr_error TYPE REF TO cx_root.
strlength = strlen( txt_in ).
DO strlength TIMES.
offset = sy-index - 1.
chr = substring( val = txt_in off = offset len = 1 ).
TRY.
icode = cl_abap_conv_out_ce=>uccpi( chr ).
CATCH cx_root INTO gr_error.
icode = 32.
ENDTRY.
IF icode < 32 OR icode > 126.
ccode = hcode = icode.
CONCATENATE result '\u' ccode INTO result.
ELSE.
CONCATENATE result chr INTO result.
ENDIF.
ENDDO.
WRITE / result.
Message was edited by: Tamas Hoznek
Added ABAP code snippet