Application Development 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: 

Issue with RFC between Non-unicode Lotus notes with SAP Unicode ECC6 system

Former Member
0 Kudos

Hi,

We are in the middle of an upgrade from 4.6c to ECC6 unicode (English and Chinese data in system). Now we are having problems with non unicode RFC from Lotus notes to SAP Unicode system.

Whenever the data is received from Lotus notes into SAP to retrieve information "text data" is not received correctly and also when sending it back from SAP to Lotus notes, characters gets jumbled-up or gets lost.

Is it any unicode issue ? Because it is trying to send 2 bytes and receiving it in 1 byte because of UTF-16 format vs Lotus notes format ?

We are not sure whether Lotus notes connector is Unicode ready or not !!

Has anyone faced similar issue before or any idea on how to resolve this ? Any help would be highly appreciated.

Thanks

1 ACCEPTED SOLUTION

sunit_s
Participant
0 Kudos

Hi

Please check the version of Lotus connector and find out if it supports Unicode communication.

You can visit the following site or find suitable info on ibm's site.

http://abhisange.wordpress.com/tag/lotus-connector-for-sap-solution/

If your lotus connector is inadequate either consider upgrading it or use abap class to convert data to code page connector understands.

If this helps award me points

Thanks

2 REPLIES 2

sunit_s
Participant
0 Kudos

Hi

Please check the version of Lotus connector and find out if it supports Unicode communication.

You can visit the following site or find suitable info on ibm's site.

http://abhisange.wordpress.com/tag/lotus-connector-for-sap-solution/

If your lotus connector is inadequate either consider upgrading it or use abap class to convert data to code page connector understands.

If this helps award me points

Thanks

Former Member
0 Kudos

Thanks. The problem was indeed the lack of support of current connector for Unicode. We moved to a recent connector.