<?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: INDEXES in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211306#M765579</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;In below select statement, u r not using any key fields like MBLNR,&lt;/P&gt;&lt;P&gt;MJAHR ,ZEILE in condition. So it should give some performance problem. You can take BWART,XAUTO,MATNR,WERKS,LGORT fields in secondary index as the same order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if it dose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Siva Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Dec 2007 11:28:47 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-12T11:28:47Z</dc:date>
    <item>
      <title>INDEXES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211305#M765578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i want to create the secondary index on mseg table.&lt;/P&gt;&lt;P&gt;here i am having select stament like this...&lt;/P&gt;&lt;P&gt;which fields can i select in the secondary index.&lt;/P&gt;&lt;P&gt;give me a brief explain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT MSEG~MBLNR&lt;/P&gt;&lt;P&gt;MSEG~BWART&lt;/P&gt;&lt;P&gt;MSEG~WERKS&lt;/P&gt;&lt;P&gt;MSEG~SHKZG&lt;/P&gt;&lt;P&gt;MSEG~MATNR&lt;/P&gt;&lt;P&gt;MSEG~ERFMG&lt;/P&gt;&lt;P&gt;MSEG~UMWRK&lt;/P&gt;&lt;P&gt;MKPF~MBLNR&lt;/P&gt;&lt;P&gt;MKPF~BUDAT&lt;/P&gt;&lt;P&gt;MSEG~XAUTO&lt;/P&gt;&lt;P&gt;MSEG~EBELN&lt;/P&gt;&lt;P&gt;INTO TABLE I_3MSEG&lt;/P&gt;&lt;P&gt;FROM MSEG&lt;/P&gt;&lt;P&gt;INNER JOIN MKPF&lt;/P&gt;&lt;P&gt;ON MSEG&lt;SUB&gt;MBLNR = MKPF&lt;/SUB&gt;MBLNR&lt;/P&gt;&lt;P&gt;WHERE MSEG~BWART IN ('301')&lt;/P&gt;&lt;P&gt;AND MSEG~MATNR IN S_MATNR&lt;/P&gt;&lt;P&gt;AND MSEG~WERKS IN S_SPLANT&lt;/P&gt;&lt;P&gt;AND MSEG~UMWRK IN S_RPLANT&lt;/P&gt;&lt;P&gt;AND MKPF~BUDAT IN S_AEDAT&lt;/P&gt;&lt;P&gt;AND MSEG~XAUTO &amp;lt;&amp;gt; 'X'&lt;/P&gt;&lt;P&gt;AND MSEG~EBELN IN S_EBELN.&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;Anand.N&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 11:19:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211305#M765578</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-12T11:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: INDEXES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211306#M765579</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;In below select statement, u r not using any key fields like MBLNR,&lt;/P&gt;&lt;P&gt;MJAHR ,ZEILE in condition. So it should give some performance problem. You can take BWART,XAUTO,MATNR,WERKS,LGORT fields in secondary index as the same order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if it dose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Siva Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 11:28:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211306#M765579</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-12T11:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: INDEXES</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211307#M765580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I wouldn't create a secondary index on a standard SAP table just to speed up one SELECT statement. There is overhead to the creation of indexes. Try to find a programming solution. Can you ensure that S_MATNR is  not empty before the SELECT? What about S_EBELN?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 14:15:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/indexes/m-p/3211307#M765580</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-12T14:15:15Z</dc:date>
    </item>
  </channel>
</rss>

