<?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: Performance Tuning in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384904#M1841061</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bunty&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT INTO TABLE, the sequence of fields already fixed by the internal table define. Does not care about the field name or field type is same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT field1 field2 ...INTO CORRESPONDING FIELDS OF TABLE, Before push the data into internal table, system need compare the SQL select fields order one by one with the internal table define, then move the corresponding value to corresponding field of itab. This process must waste time.&lt;/P&gt;&lt;P&gt;So...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Archer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Jun 2014 02:58:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-06-04T02:58:45Z</dc:date>
    <item>
      <title>Performance Tuning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384902#M1841059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;Hi ,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;I've been told to use "&lt;SPAN style="color: #ff0000;"&gt; SELECT INTO TABLE&lt;/SPAN&gt; " rather than&amp;nbsp; " &lt;SPAN style="color: #ff0000;"&gt;SELECT INTO CORRESPONDING FIELDS OF TABLE&lt;/SPAN&gt; " .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;is it necessary ??? if YES !!!!???&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;then ....&lt;SPAN style="color: #ff00ff;"&gt; WHY SO !!!????&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;Kindly explain the concept behind the performance tuning ...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;Thanks in Adv.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0000ff;"&gt;Bunty&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jun 2014 17:09:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384902#M1841059</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-06-03T17:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Tuning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384903#M1841060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;UL&gt;&lt;LI&gt;"SELECT INTO TABLE is better than 'INTO CORRESPONDING FIELDS OF' is a well established myth which is wrong.&lt;/LI&gt;&lt;LI&gt;There is an apt document for your reference written by Thomas Zloch in this regard.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A __default_attr="33976" __jive_macro_name="document" class="jive_macro_document jive_macro" data-orig-content="Why &amp;quot;INTO CORRESPONDING&amp;quot; is much better than its reputation" href="https://community.sap.com/" modifiedtitle="true" title="Why &amp;quot;INTO CORRESPONDING&amp;quot; is much better than its reputation"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Now about performance tuning, it is a very subjective term. You have to be more specific while asking about performance tuning. I would better give hints about some tcodes which you could make use while analyzing&amp;nbsp; performance such as ST05, SAT etc. You should also not forget about the code checker you are having in SE38. In addition to it have a research on SLIN tcode as well.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Philip.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jun 2014 17:21:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384903#M1841060</guid>
      <dc:creator>philipdavy</dc:creator>
      <dc:date>2014-06-03T17:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Tuning</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384904#M1841061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bunty&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT INTO TABLE, the sequence of fields already fixed by the internal table define. Does not care about the field name or field type is same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT field1 field2 ...INTO CORRESPONDING FIELDS OF TABLE, Before push the data into internal table, system need compare the SQL select fields order one by one with the internal table define, then move the corresponding value to corresponding field of itab. This process must waste time.&lt;/P&gt;&lt;P&gt;So...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Archer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jun 2014 02:58:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-tuning/m-p/10384904#M1841061</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-06-04T02:58:45Z</dc:date>
    </item>
  </channel>
</rss>

