Character Converting Problem at File Adapter

[#1]

I am having a character conversion problem bringing in a XML file into XI.

It is converting the data wrong.

I have a file adapter picking up Audit.xml encoding is utf-8, use binary mode to pick it up.

XI takes the file and converts it into a text file.

I compared the hex of Audit.xml source file and the Audit.txt file and the characters are different for a specific few.

See attached image for details

Please let me know if any additional information will help

http://i9.photobucket.com/albums/a68/tkc204/SAP%20XI/Audit.png

[sunilchandra007 · Accepted solution]

Hi Chirag,

Try with File Type as Text at both sender and receiver file adapter.

Regards,

Sunil Chandra

[Former Member · Accepted solution]

Hi Sunil,

Thanks for the response.I have tried that. I still have the same problem I have tried the following

Text - UTF-8 to Text UTF-8

Binary to Text UTF-8

UTF-8 to Binary

[sunilchandra007 · Accepted solution]

Might be the specific character is not available in UTF-8. Try File Encoding with ISO-8859-1 or UTF-16 .

Regards,

Sunil Chandra

[Former Member · Accepted solution]

I will try that, but if the XML header has

<?xml version="1.0" encoding="UTF-8" ?>

doesnt it override your xi setting?

[sunilchandra007 · Accepted solution]

Check section 16 for file encoding https://service.sap.com/sap/support/notes/821267 . Also have a look at 3.1 of http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79f... .

Regards,

Sunil Chandra

[Former Member · Accepted solution]

Hey Thanks, Ive actually have reviewed those before. The file the source system is sending to xi is also not opening up in Internet Explorer.

The source system is 1252 and outputs xml to utf-8

I think there is an issue between those two.

But since the hex is changing in XI, the source system won't look at the data.

[Former Member · Accepted solution]

HI Chirag,

Please post the Audit.txt and Audit.xml data where you feel it's getting changed.So,that we can have a look and try to solve it.

Regards,

Nutan

[Former Member · Accepted solution]

Hi Chirag,

Try like this,

Keep the sender mode as binary

and receiver channel as TEXT with Windows-1252 encoding

Regards

Suraj

[Former Member · Accepted solution]

Appears that did the trick.

The data is appearing the same as the source. I need to do additional testting to verify that the issues is resolved.

Thanks

[stefan_grube · Accepted solution]

> and receiver channel as TEXT with Windows-1252 encoding

First ask which codepage is expected by the receiver.

You cannot just put any codepage you like

[Former Member · Accepted solution]

The Source team claimed it was UTF-8. But after rigorous investigation it wasn't.