<?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 Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388435#M813614</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mr. Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have just one thing to say to you ' THANK YOU VERY MUCH '. Your suggestion is just about perfect. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Feb 2008 15:17:47 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-13T15:17:47Z</dc:date>
    <item>
      <title>Performance Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388431#M813610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am building a infoset - query report &amp;amp; one of the selection options on the selection screen is for RESB-EBELN. When i enter a Purch. Order no. &amp;amp; execute the query, it takes a very long time. This is because this field is not a primary field of this table &amp;amp; also there is no Index for this field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know is there anyway i can improve the performance without creating an index on this field? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Await inputs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 14:44:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388431#M813610</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-13T14:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388432#M813611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;RESB&lt;/STRONG&gt; is a very big table...Like 10 Million records on my system...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I have done is an INNER JOIN with MARC, so I can limit the search by WERKS and LVORM...It's still slow, but at least is better...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 14:51:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388432#M813611</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-13T14:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388433#M813612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mr. Alvaro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the inputs, as you said the RESB table i am working on has about 18 million entries. An inner-join also would not really help much. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just wanted to check with the guru's of ABAP to see if there is any way to get the same performace as I would get by creating an Index on this field. The reason i am looking for this is alternative is because i do not want to create more Indexes on this table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of now i have one alternative as suggested by you, i.e. using INNER JOINS, if there is any alternative would be glad to hear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 14:55:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388433#M813612</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-13T14:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388434#M813613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe you can use table EKET. This has EBELN in the primary key and RSNUM somewhere in the data.&lt;/P&gt;&lt;P&gt;Might be a way to quickly find reservations for a given purchase order number.&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 15:06:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388434#M813613</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2008-02-13T15:06:19Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388435#M813614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mr. Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have just one thing to say to you ' THANK YOU VERY MUCH '. Your suggestion is just about perfect. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vivek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 15:17:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issue/m-p/3388435#M813614</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-13T15:17:47Z</dc:date>
    </item>
  </channel>
</rss>

