In this case, you should check whether “Character width in target system”
is unicode or not. If it’s unicode, you should set code page of “SAP
Transport Properties” in Biztalk Admin console to either 4102 which
is SAP defined UTF-8 code page.
Then how can you test connection between SAP and Biztalk?
RFC Destination connection test
1. launch SAPGUI.
2. login.
3. excute transaction SM59(Display and maintain RFC destinations)
4. TCP/IP Connections
4.1. pick RFC destination.
5. go to special options.
6. change “Character Width in Target System”.
6.1. either Non-Unicode or Unicode.
7. test connection .
8. Unicode connection.
Configuration in Biztalk Admin Console
Non-Unicode:
1. Biztalk Administration
2. Receive PipeLine
3. Sap Transport Properties
4. Sap Authorization
4.1. code page = 0(default)
4.2. Biztalk code page = 65001(this can be varied for own situations)
Unicode:
1. Biztalk Administration
2. Receive PipeLine
3. Sap Transport Properties
4. Sap Authorization
4.1. code page = 4102
4.2. Biztalk code page = 65001
If codepage you set in Biztalk Admin Console, connection will be failed and
put error message like this.
Target system not reached
If codepage is correct,
Target is a unicode system (char.size 2)
Since char size is 2 by now, you should make sure “Count Positions in
Bytes” property for SAP schema has set to “No”. If this is “Yes”, Biztalk
will count character by byte, if not, by count of chararcters.
SAP Defined
—————
4102 : UTF-8
4103 : UTF-16
Non-Unicode