Skip to Content

sapnwrfc call to non-unicode system

Hi,

We are using the beloved Ruby gem to connect to SAP via linux environment. The website of course is utf-8 and the SAP codepage is 1100. The SAP gui codepage shows at 1160.

As per this wiki article https://wiki.scn.sap.com/wiki/display/ABAP/Character+encoding+conversion

We set our codepage in the rfc interface to match at 1100 or 1160 and we set the rfc.parameters encoding to WINDOWS_1252 or else ISO_8859_1

When we call RFC_PING, we see the following:

{"dest"=>"", "host"=>"dev.internal", "partnerHost"=>"(suppressed)", "sysNumber"=>"00", "sysId"=>"CEQ", "client"=>"010", "user"=>"(suppressed)", "language"=>"E", "trace"=>"0", "isoLanguage"=>"EN", "codepage"=>"4103", "partnerCodepage"=>"1100", "rfcRole"=>"C", "type"=>"E", "rel"=>"720", "partnerType"=>"3", "partnerRel"=>"731 ", "kernelRel"=>"721 ", "cpicConvId"=>"42534404", "progName"=>"SAPLSYST"}

If I understand correctly, sapnwrfc library expects codepage 4103 which is unicode, but our target SAP system is NOT unicode.

Can anyone explain where/how we alter the RFC processing to safely convert a user's entry to something that we can pass into SAP?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Mar 26 at 09:52 AM

    Dear Ray,

    if you go to SM59 and choose the RFC destination, which checkbox is chosen in the UNICODE tab?

    How is the line of communication set up?
    CEQ (Non-Unicode) < RFC destination > Unicode Frontend?

    Codepage 1100 is the backend codepage. Frontend Codepage 1160 is for Windows. If you have a linux environement it should be 1100 as well. Please check https://wiki.scn.sap.com/wiki/x/Oxx7H for more information on this.


    Cheers,
    Andreas

    Add comment
    10|10000 characters needed characters exceeded