<?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 Re: How to track Unicode errors in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566558#M255970</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chaitanya,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Without UCCHECK that is going to be difficult tracking the Unicode errors. When the system is upgraded, we should run all the custom program through UCCHECK so that we know which programs have errors. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And more over its easy to do and you can do this in one shot for all the programs using the selection criterial of the transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other work around is to manually look at the code and see if there are any commands specified in the UNICODE COOKBOOK for ABAP used in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;P&gt;Note : Please mark all the helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Oct 2006 08:37:23 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-10-17T08:37:23Z</dc:date>
    <item>
      <title>How to track Unicode errors</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566557#M255969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can any one give a briefing on the kind of unicode errors in SAP and how can we track the unicode errors &amp;lt;i&amp;gt;without&amp;lt;/i&amp;gt; using the transaction UCCHECK .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Oct 2006 02:51:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566557#M255969</guid>
      <dc:creator>Chaitanyat</dc:creator>
      <dc:date>2006-10-17T02:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to track Unicode errors</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566558#M255970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chaitanya,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Without UCCHECK that is going to be difficult tracking the Unicode errors. When the system is upgraded, we should run all the custom program through UCCHECK so that we know which programs have errors. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And more over its easy to do and you can do this in one shot for all the programs using the selection criterial of the transaction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other work around is to manually look at the code and see if there are any commands specified in the UNICODE COOKBOOK for ABAP used in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;P&gt;Note : Please mark all the helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Oct 2006 08:37:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566558#M255970</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-17T08:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to track Unicode errors</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566559#M255971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Ravi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the task was to check for unicode erros in non-unicode programs without using the transaction UCCHECK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Oct 2006 06:32:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566559#M255971</guid>
      <dc:creator>Chaitanyat</dc:creator>
      <dc:date>2006-10-19T06:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to track Unicode errors</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566560#M255972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chaitanya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Unicode errors can be both: SYNTAX errors and RUNTIME errors. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  UCCHECK is the better option to analyze syntax errors whereas it can not give runtime errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Maybe you can also explore and search for programs with RSUN*.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Eswar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Oct 2006 06:36:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-track-unicode-errors/m-p/1566560#M255972</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-10-19T06:36:19Z</dc:date>
    </item>
  </channel>
</rss>

