<?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: Problem with Selection-Option tables.. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-selection-option-tables/m-p/6706249#M1453158</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __default_attr="blue" __jive_macro_name="color"&gt;HI Sudha, 
&amp;lt;li&amp;gt;There is no problem with SELECT-OPTIONS, we use like that. But the problem I believe is that you are not passing full key of EKBE table only two keys out of 7 key fields. To improve performance better to create secondary indexes for BUDAT and MATNR so that it gets improved performance wise. 

Thanks
Venkat.O&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Mar 2010 01:58:23 GMT</pubDate>
    <dc:creator>venkat_o</dc:creator>
    <dc:date>2010-03-12T01:58:23Z</dc:date>
    <item>
      <title>Problem with Selection-Option tables..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-selection-option-tables/m-p/6706248#M1453157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i have developed a report in that i am using select-option fields (tables) in select statement like below,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; But this statement  is taking long time while running, is there any alternative for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; below is my code :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT ebeln ebelp bwart budat menge  belnr buzei bewtp charg bwtar matnr werks&lt;/P&gt;&lt;P&gt;                  FROM ekbe INTO CORRESPONDING FIELDS OF TABLE&lt;/P&gt;&lt;P&gt;                            it_sto WHERE ebeln IN s_ebeln&lt;/P&gt;&lt;P&gt;                                    AND ebelp IN s_ebelp&lt;/P&gt;&lt;P&gt;                                    AND budat IN s_budat&lt;/P&gt;&lt;P&gt;                                    AND matnr IN s_matnr&lt;/P&gt;&lt;P&gt;                                    AND bwart &amp;lt;&amp;gt; space .&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;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;Sudha.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Mar 2010 01:51:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-selection-option-tables/m-p/6706248#M1453157</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-03-12T01:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with Selection-Option tables..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-selection-option-tables/m-p/6706249#M1453158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __default_attr="blue" __jive_macro_name="color"&gt;HI Sudha, 
&amp;lt;li&amp;gt;There is no problem with SELECT-OPTIONS, we use like that. But the problem I believe is that you are not passing full key of EKBE table only two keys out of 7 key fields. To improve performance better to create secondary indexes for BUDAT and MATNR so that it gets improved performance wise. 

Thanks
Venkat.O&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Mar 2010 01:58:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-with-selection-option-tables/m-p/6706249#M1453158</guid>
      <dc:creator>venkat_o</dc:creator>
      <dc:date>2010-03-12T01:58:23Z</dc:date>
    </item>
  </channel>
</rss>

