<?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: SELECT query performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249643#M1527409</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check for available secondary indexes of that table and create one if required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please post performance related questions in the other forum as suggested by Abhi in the above post.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 Sep 2010 10:57:28 GMT</pubDate>
    <dc:creator>GauthamV</dc:creator>
    <dc:date>2010-09-11T10:57:28Z</dc:date>
    <item>
      <title>SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249640#M1527406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello experts!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing the performance issue in the below SELECT query. Its taking long time to execute this query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please suggest how can i improve the performance of this query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT MBLNR MATNR LIFNR MENGE WERKS BUKRS LGORT BWART INTO CORRESPONDING FIELDS OF TABLE IT_MSEG&lt;/P&gt;&lt;P&gt;    FROM MSEG&lt;/P&gt;&lt;P&gt;    WHERE MATNR IN S_MATNR&lt;/P&gt;&lt;P&gt;    AND LIFNR IN S_LIFNR&lt;/P&gt;&lt;P&gt;    AND WERKS IN S_WERKS&lt;/P&gt;&lt;P&gt;    AND BUKRS IN S_BUKRS&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;   AND XAUTO = ''&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    AND BWART IN ('541' , '542' , '543' , '544', '105' , '106').&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&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;Ankur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 09:16:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249640#M1527406</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-11T09:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249641#M1527407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This query is related to the performancee tuning. So you could have opted for the [Forum: ABAP Performance and Tuning|&lt;A class="jive_macro jive_macro_community" href="https://community.sap.com/" __jive_macro_name="community" modifiedtitle="true" __default_attr="2017"&gt;&lt;/A&gt;; for quick anwers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way your select query tries to hit &lt;STRONG&gt;MSEG&lt;/STRONG&gt; with none of the primary keys &amp;amp; top of that it uses &lt;STRONG&gt;INTO CORRESPONDING FIELDS&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to use at least some of the primary key fields of MSEG like &lt;STRONG&gt;MBLNR&lt;/STRONG&gt; &lt;STRONG&gt;MJAHR&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;ZEILE&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Abhii&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 10:19:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249641#M1527407</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-11T10:19:26Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249642#M1527408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi abhii!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for the response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;actually in this query i want all the transaction of material to a selected vendor from selection screen. there is no concept of fin year or document number. i need to find out the opening stock and closing stock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;still your suggestion was helpful.&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;Ankur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 10:28:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249642#M1527408</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-11T10:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249643#M1527409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check for available secondary indexes of that table and create one if required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please post performance related questions in the other forum as suggested by Abhi in the above post.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 10:57:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249643#M1527409</guid>
      <dc:creator>GauthamV</dc:creator>
      <dc:date>2010-09-11T10:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249644#M1527410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then you must have to look for the already available indexes in the table &lt;STRONG&gt;MSEG&lt;/STRONG&gt;. I have checked in my system, there is an index on named &lt;STRONG&gt;M          Material documents for material&lt;/STRONG&gt; with at least  three of the fields you have used in the select clause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try using thee same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise you can create your own index with the fields you have used in the where clause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Abhii&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Abhii on Sep 11, 2010 2:26 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Abhii on Sep 11, 2010 2:28 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 12:26:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249644#M1527410</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-11T12:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249645#M1527411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;create index for these table with the fields required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regards&lt;/P&gt;&lt;P&gt;S.Janagar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 13:48:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249645#M1527411</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-11T13:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249646#M1527412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the MSEG index for material is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Index MSEG~M &lt;/P&gt;&lt;P&gt;MANDT &lt;/P&gt;&lt;P&gt;MATNR &lt;/P&gt;&lt;P&gt;WERKS &lt;/P&gt;&lt;P&gt;LGORT &lt;/P&gt;&lt;P&gt;BWART &lt;/P&gt;&lt;P&gt;SOBKZ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It could be used very efficient if you supply values for MATNR, WERKS and LGORT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no index on LIFNR. IKf you want the data for specific vendor(s), you should select from EKKO first, ir has index Index EKKO~1 &lt;/P&gt;&lt;P&gt;MANDT &lt;/P&gt;&lt;P&gt;LIFNR &lt;/P&gt;&lt;P&gt;EKORG &lt;/P&gt;&lt;P&gt;EKGRP &lt;/P&gt;&lt;P&gt;BEDAT &lt;/P&gt;&lt;P&gt;You can JOIN EKKO and EKBE to get the BSEG key fields GJAHR BELNR BUZEI directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know your details but I think you can get all you need from EKKO and EKBE. You may also consider EKPO as is has a material index Index EKPO~1 &lt;/P&gt;&lt;P&gt;MANDT &lt;/P&gt;&lt;P&gt;MATNR &lt;/P&gt;&lt;P&gt;WERKS &lt;/P&gt;&lt;P&gt;BSTYP &lt;/P&gt;&lt;P&gt;LOEKZ &lt;/P&gt;&lt;P&gt;ELIKZ &lt;/P&gt;&lt;P&gt;MATKL &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you really need the (much bigger) MSEG?&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&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Sep 2010 21:41:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249646#M1527412</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2010-09-11T21:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249647#M1527413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why you are reading data from table MSEG ?&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
SELECT MBLNR MATNR LIFNR MENGE WERKS BUKRS LGORT BWART INTO CORRESPONDING FIELDS OF TABLE IT_MSEG
FROM MSEG
WHERE MATNR IN S_MATNR
AND LIFNR IN S_LIFNR
AND WERKS IN S_WERKS
AND BUKRS IN S_BUKRS
* AND XAUTO = ''
AND BWART IN ('541' , '542' , '543' , '544', '105' , '106').
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;You can read data from &lt;STRONG&gt;AUFM&lt;/STRONG&gt; table which much faster and less data than the &lt;STRONG&gt;MSEG&lt;/STRONG&gt;, But company code (ie BUKRS)  is not there, So read company code from another table like &lt;STRONG&gt;MKPF&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't used &lt;STRONG&gt;CORRESPONDING FIELDS OF&lt;/STRONG&gt;  of database table having more fields, It take more time re-arrange the data in your order.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Sep 2010 05:32:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249647#M1527413</guid>
      <dc:creator>ravi_lanjewar</dc:creator>
      <dc:date>2010-09-12T05:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249648#M1527414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the records are really huge in number, as its MSEG, you can probably go for SELECT.....ENDSELECT specifying the PACKAGE SIZE.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Sep 2010 21:47:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249648#M1527414</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-12T21:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249649#M1527415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;Don't used CORRESPONDING FIELDS OF of database table having more fields, It take more time re-arrange the data in your order.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is simply not true. Data are not re-arranged at all. Trace and analyze SELECT statement for both alternatives.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Always use INTO CORRESPONDING FIELDS OF&lt;/STRONG&gt; because it is fail-safe and does not cost performance.&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&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2010 11:51:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249649#M1527415</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2010-09-13T11:51:37Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249650#M1527416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;Always use INTO CORRESPONDING FIELDS OF because it is fail-safe and does not cost performance.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Wish I could give you 10-points for that, but I leave that to the OP &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2010 12:04:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249650#M1527416</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-13T12:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249651#M1527417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Give this a try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;SELECT b~mblnr
       b~matnr
       b~lifnr
       b~menge
       b~werks
       b~bukrs
       b~lgort
       b~bwart
FROM        mard AS a
INNER JOIN  mseg AS b
ON  a~matnr EQ b~matnr
AND a~werks EQ b~werks
AND a~lgort EQ b~lgort
INTO TABLE it_mseg
WHERE a~matnr IN s_matnr
AND   a~werks IN s_werks
AND   b~bwart IN ('541' , '542' , '543' , '544', '105' , '106')
AND   b~lifnr IN s_lifnr
AND   b~bukrs IN s_bukrs.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2010 16:30:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249651#M1527417</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-13T16:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249652#M1527418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;or  with some readability:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;SELECT mseg~mblnr
       mseg~matnr
       mseg~lifnr
       mseg~menge
       mseg~werks
       mseg~bukrs
       mseg~lgort
       mseg~bwart
FROM        mard
INNER JOIN  mseg
ON  mard~matnr EQ mseg~matnr
AND mard~werks EQ mseg~werks
AND mard~lgort EQ mseg~lgort
INTO TABLE it_mseg
WHERE mard~matnr IN s_matnr
AND   mard~werks IN s_werks
AND   mseg~bwart IN ('541' , '542' , '543' , '544', '105' , '106')
AND   mseg~lifnr IN s_lifnr
AND   mseg~bukrs IN s_bukrs.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2010 16:33:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249652#M1527418</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2010-09-13T16:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249653#M1527419</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;thanks for the response. Now i am using index M of MSEG table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i have some more fileds in my Select query as compared to that in Index M of the table. Although I am putting the fields in the same order as in the index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But as the fields in SELECT query are more than in Index, will index work?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer the below Select query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT  MATNR WERKS LGORT BWART SOBKZ  LIFNR MBLNR MENGE BUKRS  INTO CORRESPONDING FIELDS OF TABLE IT_MSEG&lt;/P&gt;&lt;P&gt;FROM MSEG&lt;/P&gt;&lt;P&gt;WHERE MATNR IN S_MATNR&lt;/P&gt;&lt;P&gt;AND WERKS IN S_WERKS&lt;/P&gt;&lt;P&gt;AND BWART IN ('541' , '542' , '543' , '544', '105' , '106').&lt;/P&gt;&lt;P&gt;AND LIFNR IN S_LIFNR&lt;/P&gt;&lt;P&gt;AND BUKRS IN S_BUKRS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please reply&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Sep 2010 04:15:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249653#M1527419</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-14T04:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249654#M1527420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know but LIFNR field is blank in AUFM table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you help me what could be the reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No doubt AUFM is much faster than MSEG. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ankur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Sep 2010 05:15:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249654#M1527420</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-14T05:15:22Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249655#M1527421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ankur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
I don't know but LIFNR field is blank in AUFM table
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know the exact reason of it,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But know you have the key fields of MSEG table now (ie. after reading data from aufm) using that you can read the table mseg for LIFNR fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will give better performance than direct fetch data from mseg table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Sep 2010 13:23:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249655#M1527421</guid>
      <dc:creator>ravi_lanjewar</dc:creator>
      <dc:date>2010-09-14T13:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: SELECT query performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249656#M1527422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;/SPAN&gt;Moderator message - Please see &lt;SPAN __jive_macro_name="thread" id="1283414"&gt;&lt;/SPAN&gt; before posting - post locked&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a performance problem, there are some testing that you have to do before posting here. Not doing that just wastes everyone's time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob{color&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Sep 2010 13:32:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/select-query-performance-issue/m-p/7249656#M1527422</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-14T13:32:08Z</dc:date>
    </item>
  </channel>
</rss>

