<?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 Unicode Conversion approach in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023425#M1609051</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;During Unicode approach isit possible to do the conversion of custom and standard program to unicode and make the system live and later on do the data conversion with business downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason i am asking so as to reduce the business down time. We are going for CU&amp;amp;UC and donot want a long business downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if there are any approach where we can do the data conversion in the later phase.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rajat Sarkar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Aug 2011 10:16:17 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-08-04T10:16:17Z</dc:date>
    <item>
      <title>Unicode Conversion approach</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023425#M1609051</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;During Unicode approach isit possible to do the conversion of custom and standard program to unicode and make the system live and later on do the data conversion with business downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason i am asking so as to reduce the business down time. We are going for CU&amp;amp;UC and donot want a long business downtime.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if there are any approach where we can do the data conversion in the later phase.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Rajat Sarkar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2011 10:16:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023425#M1609051</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-04T10:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: Unicode Conversion approach</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023426#M1609052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer &lt;A href="http://wiki.sdn.sap.com/wiki/display/unicode/Project" target="test_blank"&gt;http://wiki.sdn.sap.com/wiki/display/unicode/Project&lt;/A&gt;&lt;EM&gt;Planning&lt;/EM&gt;-&lt;EM&gt;Single&lt;/EM&gt;Code&lt;EM&gt;Page&lt;/EM&gt;System&lt;/P&gt;&lt;P&gt;Above suggests performing the ABAP Unicode enabling well in advance. And to test the DEV unicode enabled ABAP in a non-UC QA system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However I am not sure if the same should be done for a live/production system. I would consider that risky.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Srikishan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2011 11:24:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023426#M1609052</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-04T11:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unicode Conversion approach</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023427#M1609053</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;please have a look at:&lt;/P&gt;&lt;P&gt;&lt;A href="http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&amp;amp;_OBJECT=011000358700000620342009E" target="test_blank"&gt;http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&amp;amp;_OBJECT=011000358700000620342009E&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Page 21&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Excerpt begin:&lt;/P&gt;&lt;P&gt;1) Start release &amp;gt;= SAP NetWeaver AS 6.20&lt;/P&gt;&lt;P&gt;&amp;gt; UCCHECK can be run before or during Unicode conversion&lt;/P&gt;&lt;P&gt;2) Start release &amp;lt;= 4.6C (CU&amp;amp;UC or TU&amp;amp;UC*)&lt;/P&gt;&lt;P&gt;&amp;gt; Execute the whole UCCHECK procedure in the SBX Unicode system&lt;/P&gt;&lt;P&gt;&amp;gt; Upgrade the DEV system to SAP ERP 6.0 (Non-Unicode or Unicode) and execute UCCHECK (Additional Maintenance System necessary)&lt;/P&gt;&lt;P&gt;Excerpt End.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore if you have a 4.6c system (or lower) as source system, then the Unicode enabling procedure (UCCHECK) cannot be separated from the actual Unicode conversion (Export / Import). In case of NW 6.20 or higher, you can do most of the enabling before the conversion (you will still need a rework after the conversion).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Nils Buerckel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2011 11:38:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/unicode-conversion-approach/m-p/8023427#M1609053</guid>
      <dc:creator>nils_buerckel</dc:creator>
      <dc:date>2011-08-04T11:38:11Z</dc:date>
    </item>
  </channel>
</rss>

