<?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 SAPSCRIPT MAIN BOTTOM PERFORMANCE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sapscript-main-bottom-performance/m-p/1848409#M359651</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;we have a massive performance problem with sapscript.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SAPSCRIPT we use WRITE_FORM with BOTTOM in MAIN WINDOW. When using APPEND, sapscript debugger shows that for every text element all text elements which have been triggered for BOTTOM/APPEND before are triggered again. That means the first is triggered again when the second is triggered and so on. When . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The math genius may calculate what that means for more than 100 text elements triggered: more than 10.000 times the text element gets triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried function 'SET' but then only the last element triggered is in the printed output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for the many text elements is our special technique to print different character sizes in left and right area of bottom: We use a paragraph format with 1 point Line Spacing, i.e. create 7 lines empty and then one with 8pt character format text, then 9 line space, then 1 line with a tab to the right side and a 10 point character formattted text. - The customer wants payment conditions on the left in 6 point, SUM information in 11 point on the right - everything at the bottom of the last (which may be the first) page of the invoice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought the idea of the 1 point line spacing technique was good but now (unicode system!) it takes up to 5 seconds to create one invoice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas are welcome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens Li&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Jan 2007 18:58:45 GMT</pubDate>
    <dc:creator>Clemenss</dc:creator>
    <dc:date>2007-01-31T18:58:45Z</dc:date>
    <item>
      <title>SAPSCRIPT MAIN BOTTOM PERFORMANCE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sapscript-main-bottom-performance/m-p/1848409#M359651</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;we have a massive performance problem with sapscript.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In SAPSCRIPT we use WRITE_FORM with BOTTOM in MAIN WINDOW. When using APPEND, sapscript debugger shows that for every text element all text elements which have been triggered for BOTTOM/APPEND before are triggered again. That means the first is triggered again when the second is triggered and so on. When . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The math genius may calculate what that means for more than 100 text elements triggered: more than 10.000 times the text element gets triggered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried function 'SET' but then only the last element triggered is in the printed output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for the many text elements is our special technique to print different character sizes in left and right area of bottom: We use a paragraph format with 1 point Line Spacing, i.e. create 7 lines empty and then one with 8pt character format text, then 9 line space, then 1 line with a tab to the right side and a 10 point character formattted text. - The customer wants payment conditions on the left in 6 point, SUM information in 11 point on the right - everything at the bottom of the last (which may be the first) page of the invoice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought the idea of the 1 point line spacing technique was good but now (unicode system!) it takes up to 5 seconds to create one invoice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas are welcome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens Li&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 18:58:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sapscript-main-bottom-performance/m-p/1848409#M359651</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-01-31T18:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: SAPSCRIPT MAIN BOTTOM PERFORMANCE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sapscript-main-bottom-performance/m-p/1848410#M359652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;we circumvented the problem using function WRITE_FORM_LINES.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Apr 2007 13:16:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sapscript-main-bottom-performance/m-p/1848410#M359652</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-04-12T13:16:25Z</dc:date>
    </item>
  </channel>
</rss>

