Special character in File to IDoc

[Former Member]

Hi,

am working on file to Idoc scenario.

The data is populated as expected in to the segments but when i see the idoc in the receiving system the special characters are replaced by #

For ex

how LII u201Cexceeds industry benchmarks and defeats stereotypesu201D

is cming as LII #exceeds industry benchmarks and defeats stereotypes#

Any suggestions to display the special characters.

[Former Member · Accepted solution]

Please check if this note helps 1004368

[Former Member · Accepted solution]

Hi,

In ur XI system go to sm59>select ur rfc destinition>MDMP & Unicode--->Change the "Communication Type with Target System" to Unicode.

Thanks,

Sudhansu

[stefan_grube]

> how LII u201Cexceeds industry benchmarks and defeats stereotypesu201D

The u201C and u201D are not part of most common codepages, like iso-8859-1.

I am not sure, if there is any solution for that issue.

Could you change the characters to " (quote)?

http://en.wikipedia.org/wiki/ISO/IEC_8859-1

Regards

Stefan

[Former Member]

In your File Sender channel you can set the File Encoding Scheme of your choice. We had a similar case where special characters were seen as # . Once we changed the Encoding scheme to ISO-8859-1 it worked fine.

Refer to the below link

http://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm

-Mala

[Former Member]

Prem5405 ,

I actually tried to change but the receiver system in non unicode and hence its not changing.

-->are you sure...?

-->did you check with your basis teams about this ?

Regards,

[Former Member]

U can check this note. The receiving system should be Unicode if we need to set that parameter.

Note 875767 - ABAP runtime error CALL_FUNCTION_NO_UNICODE_SERVER

[prateek]

Try changing the RFC destination in receiver SAP system to Unicode. This RFC destination name could be seen from Idoc receiver channel.

Regards,

Prateek

[Former Member]

Thanks prateek.

I actually tried to change but the receiver system in non unicode and hence its not changing.

Is there any other possiblity

[former_member200962]

I think even in SXMB_MONI the special characters are replaced....can you check if you are getting the required special characters in the payload in SXMB_MONI.

If feasible try using the CDATA element to enclose your nodes which contain special characters.....if no straight method works out for you.

Regards,

Abhishek.

[Former Member]

its perfect in SXMB_MONI getting the problem in the receiving system only.

I dont think the second option is viable.

Any other suggestion pls

[Former Member]

its perfect in SXMB_MONI getting the problem in the receiving system only.

I dont think the second option is viable.

Any other suggestion pls