Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

RFC destination definition with non-unicode external program

Former Member
0 Likes
1,052

Hello All,

we have one issue with our RFID system connecting to WM system (SWD).

For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.

But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.

We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.

To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)

Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.

Anyone know how to help ?

Hello All,

we have one issue with our RFID system connecting to WM system (SWD).

For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.

But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.

We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.

To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)

Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.

Anyone know how to help ?

4 REPLIES 4
Read only

Former Member
0 Likes
844

Hi,

Try changing the code page value in SM59.

Thanks,

Best regards,

Prashant

Read only

0 Likes
844

Hi Prashant,

How can I change code page in sm59?

Thanks,

Jeongbae

Read only

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Likes
844

Hi Jeongbae,

as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.

In earlier releases, this is not possible.

In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.

Please check SAP note 788239.

Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.

In addition I would recommend to have a look at SAP note 1021459.

However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).

For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !

Best regards,

Nils Buerckel

SAP AG

Read only

Former Member
0 Likes
844

Buddy,

We are facing the same problem with you !!

Pls kindly tell if you have already sovled the issue ?

Looking forward to your answer .