Not able to read Special character in reciver side

[Former Member]

Hi experts,

I am doing one file to file tuneeling where I am picking source file from legacy sytem and puting the same file into Sap system without any transformation or convertion. However facing one probem there is a text BOMPREÇO coming in the source file same text my sender adapter is picking I can view the same text in my MONI payload but when the same file is getting placed in SAP application server it is coming as BOMPRE?O. I have used many encoding option including ISO-8859-2 and others but no result when I am changing it to binary mode from text mode it is coming as BOMPRE#O same for UTF-8 and ascii encoding option.

Please guide me in this regards

Regards,

Saurabh

[Cortex2k]

Hi Saurabh

How do you put the file on the application server?

Might help to have a look at:

[How to Work with Character Encodings in Process Integration (NW7.0)|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]

Best regards,

Chris

[Former Member]

Hi,

If you are looking your file in AL11 directory then I think you are getting the file in correct format. This is happening due to disply property of AL11. Try to open the file with internet explorer and then chose the correct format and see if you get the in correct format. If yes then your file is correct.

Regards,

Sarvesh

[Former Member]

Hi Sarvesh,

Thanks for the quick reply.

I am checking the file in al11 only. Now I domnloaded this file to my local directory .there also the file is coming with BOMPRE?O only. Secondly if it is a view problem then it shoud throw some junk character not ? .This is my doubt .However not sure....Please update me if i have not understood your point fully.

regards,

Saurabh

[Former Member]

Hi,

AL11 dir never shows the correct fomat, it contains some junk char.

Actually I forgot to tell you in my previous reply that even if you download the file it will not show the correct symbol. The correct symbol can be seen at either on receiver legacy system or by using a receiver FTP adapter to write the file direclty on your local machine.

But at the same time you have to find the correct encoding, I guess when you got # in your file then the encoding was correct.

Regards,

Sarvesh

[Former Member]

Hi Sarvesh,

your reply make some sense thats why I have already awarded point to you.However I have one confusion that as you have mentioned when it was coming # for special character then it was correct but it was producing # when I put the receiver CC in binary mode as well as when I put it into UTF -8 also so what is your advice finally I should put ReciverCC in which mode. binary or UTF-8

Thanks&Regard,

Saurabh

[Former Member]

Hi,

Well I can recommend to use "Text" mode rather using Binary and secondly as your special text comes under "ISO 8859-1, 2, 3, 9, 14, 15, 16" as per below link, so try with ISO encoding.

http://en.wikipedia.org/wiki/Windows-1250 (see the second table in row C7 and click on symbol to know more)

Regards,

Sarvesh