cancel
Showing results for 
Search instead for 
Did you mean: 

Codepage-Issue using PI-Proxies

Former Member
0 Kudos

Hi,

I have following scenario: HTTP-Sender (PlainHTTP) --> PI --> ABAB Server Proxy. The sender sends a xml-file into PI with encoding="utf-8". Due to this encoding the message contains some encoded letters like 'ü' for 'ü' for example. So it uses 2Bytes for the character 'ü' in this case.

The PI sends this message further to the Proxy-Receiver which is calling a BAPI (lets say BAPI_PATIENT_CREATE). This BAPI now creates a patient with a patientname like 'Müller' instead of 'Müller'

PI & Receiver-system are both unicode systems.

Can somebody plz tell me how I can solve this issue?

Many thx,

Gernot

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi,

I've found out the reason for this problem.

I've used the RWB-Componentmonitorning feature for sending test messages to the IE. So I've copied the message into the field. This was the problem because by copying a UTF-8 encoded character e.g. ü it looks correctly but it isn't correct. This problem can also occur when you save files with a wrong encoding.

Anyway: I've send the message again from the original sender system and my xsl-Transformation works perfect (as it is also described in the link above).

Many thx for all your help.

Best Regards,

Gernot

stefan_grube
Active Contributor
0 Kudos

Hi Gernot,

Could you check, if the name is correct in the XI message?

Could you check also, if the value in the data base is wrong? It could be an issue with displaying the name, for example with an HTML page.

The error cannot happen in the connection PI -> IS-H as the ü would be displayed different. It could happen only in the connection sender -> PI or it is a display issue.

Regards

Stefan

Former Member
0 Kudos

Hi,

thx for all your input. I guess that we didn't hit this issue so far.

I don't want to do any unicode-conversion in xi because this shouldn't be nessecary in my scenario. I just want to pass the xml data (UTF-8) further to the SAP-Receiver (IS-H; UTF-8). My opinion is that the receiver has to display the data correctly with codepage 4102, right? Do I have any mistakes in my line of thought?

Many thx,

Gernot

Former Member
0 Kudos

I have a similar problem since using PI 7.0. How can I check which codepage is set in the XI system?

Thanks

Thomas

Former Member
0 Kudos

try this FM SWA_CHECK_SERVER_CODEPAGE

Former Member
0 Kudos

Hi,

thx for your info. We have now codepage 4200 (SAP Unicode) for XI and the receiver system. It's not recommended to change this.

Primarily I thought that when the 2Byte character comes from the sender and goes to the receiver (as a 2Byte character) via PI the Receiver System should display this information correctly. Maybe it's a display issue?

Who can help here?

Thx,

Gernot

Former Member
0 Kudos

Hi Gernot,

Check this guide

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/502991a2-45d9...

Also, have a look at what Stefan has to say here

Regards,

Jai Shankar

Former Member
0 Kudos

ceck these code pages

1100 SAP internal, like ISO 8859-1 (00697/00819)

1180 Transliteration from Latin-2 (...) to Latin-1

1401 SAP internal, like ISO 8859-2

1500 SAP-internal, like ISO 8859-5

1610 SAP-internal, like ISO 8859-9 (Latin-5)

1700 SAP-internal, like ISO 8859-7 (Greek)

1800 SAP-internal, like ISO 8859-8 (Hebrew)

1810 SAP-internal, like ISO 8859-8 (Hebrew)

1900 SAP-internal, like ISO 8859-4 (Litauian)

6100 SAP Unification (ISO2 with ISO7 D7F7 and ISO1 FF)

6110 SAP-Unification with ISO 8859-1 view

6120 SAP-Unification, ISO 8859-2 view

6180 SAP-Unification Japanese View

6190 SAP-Unification, ISO 8859-9 (Latin Nr.5) view

6200 SAP Asian Unification (ASCIISJIS1Asian)

6230 SAP AsianUnification MDMP (Trad.Chinese + SJIS1)

6240 SAP AsianUnification MDMP (simp. Chinese + SJIS1)

6250 SAP AsianUnification MDMP (Korean + SJIS1)

6280 SAP AsianUnification MDMP (Jap. without SB kana)

6300 SAP Euro Japan (ISO1 + SJIS1)

6400 SAP Silk Road (ISO7 + SJIS1)

6500 SAP Diocletian (ISO1 with ISO7 D7 and F7)

6510 SAP-Diocletian with ISO 8859-1 view

6570 SAP-Diocletian with ISO 8859-7 (Greek) view

6600 SAP Nagamasa (Thai + SJIS1)

6700 SAP Transiberian (ISO5 + SJIS1)

8000 Shift JIS

8300 Traditional Chinese

8340 Traditional Chinese HKSCS Vers.1 System Code Page

8400 Simplified Chinese

8500 Koreanisch

8600 Thai Codepage ISO988/2533

8700 ISO8859-6 Arabic for system code page

Former Member
0 Kudos

We had similar issues with the Greek Character set and we set the codepage to 1100.