<?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: convert_otf in unicode system in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/convert-otf-in-unicode-system/m-p/1578048#M260979</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;CONVERT_OTF packs two byte into one character of i-tab LINES on unicode systems. If you pass this via RFC to non-unicode systems data ist lost. The table contents are bytes when if the data type is character. The conversion routines between unicode and non-unicode do not know about this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the function module contains an export paramter BIN_FILE. This parameter is of type XSTRING, which has always a byte-representation. This datatype will not be converted between RFC-calls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Mar 2007 09:52:30 GMT</pubDate>
    <dc:creator>gnther_berger</dc:creator>
    <dc:date>2007-03-21T09:52:30Z</dc:date>
    <item>
      <title>convert_otf in unicode system</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/convert-otf-in-unicode-system/m-p/1578047#M260978</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;we have switched a CRM4.0 system from non-unicode to unicode. In this context we became two problems with the result of the function module 'CONVERT_OTF'. We call the function Module following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  call function 'CONVERT_OTF'&lt;/P&gt;&lt;P&gt;   exporting&lt;/P&gt;&lt;P&gt;     format                      = 'PDF'&lt;/P&gt;&lt;P&gt;     max_linewidth               = 132&lt;/P&gt;&lt;P&gt;     copynumber                  = 0&lt;/P&gt;&lt;P&gt;   importing&lt;/P&gt;&lt;P&gt;     bin_filesize                = lv_bin_filesizepdf&lt;/P&gt;&lt;P&gt;    tables&lt;/P&gt;&lt;P&gt;     otf                         = it_otfdata&lt;/P&gt;&lt;P&gt;     lines                       = lt_lines_pdf&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the otf tabel is generated by a Smartform.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Noticeable is, that the pdf table in the unicode system has similarly only the half quantity of rows than in the non-unicode system. (The parameter FLATE_COMPR_OFF in Report RSTXPDF3 allways is on)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Problem&lt;/P&gt;&lt;P&gt;We send the pdf table (lt_lines_pdf) via RFC to a non-unicode R/3 system and save it there on the file system. After switching to unicode, the document in the RFC system is damaged an cannot processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Problem&lt;/P&gt;&lt;P&gt;We transform the lt_lines_pdf for an archive in the following way.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;data: ls_data    type char1024&lt;/P&gt;&lt;P&gt;    , lv_134     type char134&lt;/P&gt;&lt;P&gt;    , ls_lines   type tline&lt;/P&gt;&lt;P&gt;    , lt_data    type standard table of tbl1024&lt;/P&gt;&lt;P&gt;    .&lt;/P&gt;&lt;P&gt;field-symbols: &amp;lt;fs&amp;gt; type tbl1024.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;assign ls_data to &amp;lt;fs&amp;gt; casting.&lt;/P&gt;&lt;P&gt;  lv_count = 0.&lt;/P&gt;&lt;P&gt;  loop at lt_lines_pdf into ls_lines.&lt;/P&gt;&lt;P&gt;    lv_134 = ls_lines.&lt;/P&gt;&lt;P&gt;    lv_offset = lv_count.&lt;/P&gt;&lt;P&gt;    lv_count = lv_count + 134.&lt;/P&gt;&lt;P&gt;    if lv_count &amp;lt; 1024.&lt;/P&gt;&lt;P&gt;      ls_data+lv_offset(134) = lv_134.&lt;/P&gt;&lt;P&gt;    else.&lt;/P&gt;&lt;P&gt;      lv_count = lv_count - 1024.&lt;/P&gt;&lt;P&gt;      lv_begin = 134 - lv_count.&lt;/P&gt;&lt;P&gt;      ls_data+lv_offset(lv_begin) = lv_134(lv_begin).&lt;/P&gt;&lt;P&gt;      append &amp;lt;fs&amp;gt; to lt_data.&lt;/P&gt;&lt;P&gt;      clear ls_data.&lt;/P&gt;&lt;P&gt;      if lv_count &amp;gt; 0.&lt;/P&gt;&lt;P&gt;        ls_data = lv_134+lv_begin(*).&lt;/P&gt;&lt;P&gt;      endif.&lt;/P&gt;&lt;P&gt;    endif.&lt;/P&gt;&lt;P&gt;  endloop.&lt;/P&gt;&lt;P&gt;  if ls_data is not initial.&lt;/P&gt;&lt;P&gt;    append &amp;lt;fs&amp;gt; to lt_data.&lt;/P&gt;&lt;P&gt;  endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We need lt_data for the FM 'SCMS_AO_TABLE_CREATE'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope anybody can help me, I invest already much time in this problem!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Sep 2006 13:19:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/convert-otf-in-unicode-system/m-p/1578047#M260978</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-13T13:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: convert_otf in unicode system</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/convert-otf-in-unicode-system/m-p/1578048#M260979</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;CONVERT_OTF packs two byte into one character of i-tab LINES on unicode systems. If you pass this via RFC to non-unicode systems data ist lost. The table contents are bytes when if the data type is character. The conversion routines between unicode and non-unicode do not know about this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However the function module contains an export paramter BIN_FILE. This parameter is of type XSTRING, which has always a byte-representation. This datatype will not be converted between RFC-calls.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:52:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/convert-otf-in-unicode-system/m-p/1578048#M260979</guid>
      <dc:creator>gnther_berger</dc:creator>
      <dc:date>2007-03-21T09:52:30Z</dc:date>
    </item>
  </channel>
</rss>

