<?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 Open data set / code page in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356340#M1399718</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am sending file to print server  and i am accounting problems with  special characters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In first version of  program  ( please see the code below ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"OPEN DATASET g_filename  FOR OUTPUT IN TEXT MODE ENCODING DEFAULT." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The special characters l from German and French   alphabet were NOT printed properly  , and we had  some nonsense results . Other '"Normal "characters  like A , B... are printed without errors . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To prevent this error i wrote new line of code for open data set ( below ). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"OPEN DATASET g_filename FOR OUTPUT IN   LEGACY TEXT MODE CODE PAGE '4110'  IGNORING CONVERSION ERRORS." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was working only when FTP was NOT used  , when FTP was used i had  following short  dump. &lt;/P&gt;&lt;P&gt;I am working in SAP release 6.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please Advice &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SHORT DUMP Message : &lt;/P&gt;&lt;P&gt;What happened? &lt;/P&gt;&lt;P&gt;    The conversion of texts in code page '4102' to code page '4110' is not &lt;/P&gt;&lt;P&gt;    supported here. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The current ABAP program 'SAPLZPRN_AUTO_LBL' had to be interrupted because &lt;/P&gt;&lt;P&gt;     incorrect &lt;/P&gt;&lt;P&gt;    data would have been created by the conversion. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error analysis &lt;/P&gt;&lt;P&gt;    An exception occurred that is explained in detail below. &lt;/P&gt;&lt;P&gt;    The exception, which is assigned to class 'CX_SY_CODEPAGE_CONVERTER_INIT', was &lt;/P&gt;&lt;P&gt;     not caught in &lt;/P&gt;&lt;P&gt;    procedure "Z_TRANSFER_FILE" "(FUNCTION)", nor was it propagated by a RAISING &lt;/P&gt;&lt;P&gt;     clause. &lt;/P&gt;&lt;P&gt;    Since the caller of the procedure could not have anticipated that the &lt;/P&gt;&lt;P&gt;    exception would occur, the current program is terminated. &lt;/P&gt;&lt;P&gt;    The reason for the exception is: &lt;/P&gt;&lt;P&gt;    Possibly, one of the codepages '4102' or '4110' - needed for the &lt;/P&gt;&lt;P&gt;    conversion - is unknown to the system. Another option is, that a Unicode &lt;/P&gt;&lt;P&gt;     codepage was specified for a file in LEGACY MODE, which is not allowed. &lt;/P&gt;&lt;P&gt;    Additional parameters for the codepage conversion (as , for example, the &lt;/P&gt;&lt;P&gt;     replacement character) might have invalid values. You can find further &lt;/P&gt;&lt;P&gt;    information under 'Inernal notes'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If the problem occurred at opening, reading, or writing of a file, then &lt;/P&gt;&lt;P&gt;    the file name was '/te/mm/labels/0488_20091208_051317_EC008119_01_001.dd'. &lt;/P&gt;&lt;P&gt;     (Further information about this file: " X ")&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Dec 2009 11:31:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-12-08T11:31:16Z</dc:date>
    <item>
      <title>Open data set / code page</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356340#M1399718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am sending file to print server  and i am accounting problems with  special characters &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In first version of  program  ( please see the code below ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"OPEN DATASET g_filename  FOR OUTPUT IN TEXT MODE ENCODING DEFAULT." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The special characters l from German and French   alphabet were NOT printed properly  , and we had  some nonsense results . Other '"Normal "characters  like A , B... are printed without errors . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To prevent this error i wrote new line of code for open data set ( below ). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"OPEN DATASET g_filename FOR OUTPUT IN   LEGACY TEXT MODE CODE PAGE '4110'  IGNORING CONVERSION ERRORS." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was working only when FTP was NOT used  , when FTP was used i had  following short  dump. &lt;/P&gt;&lt;P&gt;I am working in SAP release 6.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please Advice &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SHORT DUMP Message : &lt;/P&gt;&lt;P&gt;What happened? &lt;/P&gt;&lt;P&gt;    The conversion of texts in code page '4102' to code page '4110' is not &lt;/P&gt;&lt;P&gt;    supported here. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    The current ABAP program 'SAPLZPRN_AUTO_LBL' had to be interrupted because &lt;/P&gt;&lt;P&gt;     incorrect &lt;/P&gt;&lt;P&gt;    data would have been created by the conversion. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error analysis &lt;/P&gt;&lt;P&gt;    An exception occurred that is explained in detail below. &lt;/P&gt;&lt;P&gt;    The exception, which is assigned to class 'CX_SY_CODEPAGE_CONVERTER_INIT', was &lt;/P&gt;&lt;P&gt;     not caught in &lt;/P&gt;&lt;P&gt;    procedure "Z_TRANSFER_FILE" "(FUNCTION)", nor was it propagated by a RAISING &lt;/P&gt;&lt;P&gt;     clause. &lt;/P&gt;&lt;P&gt;    Since the caller of the procedure could not have anticipated that the &lt;/P&gt;&lt;P&gt;    exception would occur, the current program is terminated. &lt;/P&gt;&lt;P&gt;    The reason for the exception is: &lt;/P&gt;&lt;P&gt;    Possibly, one of the codepages '4102' or '4110' - needed for the &lt;/P&gt;&lt;P&gt;    conversion - is unknown to the system. Another option is, that a Unicode &lt;/P&gt;&lt;P&gt;     codepage was specified for a file in LEGACY MODE, which is not allowed. &lt;/P&gt;&lt;P&gt;    Additional parameters for the codepage conversion (as , for example, the &lt;/P&gt;&lt;P&gt;     replacement character) might have invalid values. You can find further &lt;/P&gt;&lt;P&gt;    information under 'Inernal notes'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    If the problem occurred at opening, reading, or writing of a file, then &lt;/P&gt;&lt;P&gt;    the file name was '/te/mm/labels/0488_20091208_051317_EC008119_01_001.dd'. &lt;/P&gt;&lt;P&gt;     (Further information about this file: " X ")&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 11:31:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356340#M1399718</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-08T11:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Open data set / code page</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356341#M1399719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;solution is given in the error message !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Another option is, that a Unicode codepage was specified for a file in LEGACY MODE, which is not allowed."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 16:59:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356341#M1399719</guid>
      <dc:creator>franois_henrotte</dc:creator>
      <dc:date>2009-12-08T16:59:14Z</dc:date>
    </item>
    <item>
      <title>Re: Open data set / code page</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356342#M1399720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes that is correct ,&lt;/P&gt;&lt;P&gt;Now I reverted code . but initial problem still persists . &lt;/P&gt;&lt;P&gt;Printing special characters gives errors.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 17:01:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356342#M1399720</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-08T17:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Open data set / code page</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356343#M1399721</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;check with your basis team to see if neccessary support packs are installed... search for SAP notes...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 18:56:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356343#M1399721</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2009-12-08T18:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: Open data set / code page</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356344#M1399722</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;Also check the character set supported by the Printer. Printer configuration should also be checked on SAP side to determine character set and code page using SPAD. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nishad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Dec 2009 19:10:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/open-data-set-code-page/m-p/6356344#M1399722</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-08T19:10:23Z</dc:date>
    </item>
  </channel>
</rss>

