<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Inbound IDOC with UNICODE issues in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-idoc-with-unicode-issues/m-p/1073507#M95579</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are trying to send in an IDOC with Romanian characters that are outside of latin-1.  We have upgraded our 4.7 SAP system to be UNICODE, but when loading these characters via IDOC they are not being represented correctly in R/3.  We have tried setting our login language to RO when doing the input and it doesn't seem to matter.  Is there a setting somewhere that we are missing to designate an inbound IDOC as UTF-8?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darrin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Oct 2005 13:00:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-10-21T13:00:03Z</dc:date>
    <item>
      <title>Inbound IDOC with UNICODE issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-idoc-with-unicode-issues/m-p/1073507#M95579</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are trying to send in an IDOC with Romanian characters that are outside of latin-1.  We have upgraded our 4.7 SAP system to be UNICODE, but when loading these characters via IDOC they are not being represented correctly in R/3.  We have tried setting our login language to RO when doing the input and it doesn't seem to matter.  Is there a setting somewhere that we are missing to designate an inbound IDOC as UTF-8?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darrin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Oct 2005 13:00:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-idoc-with-unicode-issues/m-p/1073507#M95579</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-21T13:00:03Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound IDOC with UNICODE issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-idoc-with-unicode-issues/m-p/1073508#M95580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Darrin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if the sender of the IDOC is an external RFC program, you should use the "Codepage" parameter in the logon string, to declare your character set. The SAP RFC lib will then translate between external and R/3 internal codepage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you find my answer useful, please don't forget the reward.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Juergen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Oct 2005 14:55:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-idoc-with-unicode-issues/m-p/1073508#M95580</guid>
      <dc:creator>former_member225448</dc:creator>
      <dc:date>2005-10-21T14:55:26Z</dc:date>
    </item>
  </channel>
</rss>

