<?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: Matchcode replaced with View in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576622#M1756114</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;you have complicated your join query. please try this join condition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EKKO EBELN = EKPO EBELN&lt;/P&gt;&lt;P&gt;EKKO EBELN = EKET EBELN&lt;/P&gt;&lt;P&gt;EKPO EBELP = EKET EBELP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or else&lt;/P&gt;&lt;P&gt;if you know how to get data ahead of time from EKKO. Get that and then query EKPO and EKET.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;swanand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Aug 2013 19:25:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-08-02T19:25:50Z</dc:date>
    <item>
      <title>Matchcode replaced with View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576621#M1756113</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;&lt;/P&gt;&lt;P&gt;We have created Views instead of Macthcode ID. And we have fetched data from view instead of match code and the performance of the program is very poor now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Details of Matchcode:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Primary table&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EKKO&lt;/P&gt;&lt;P&gt;Secondary tables&amp;nbsp;&amp;nbsp; EKPO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EKET&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Selection condition for Matchcode ID:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Table&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MC field&amp;nbsp;&amp;nbsp;&amp;nbsp; Data elem.&amp;nbsp;&amp;nbsp; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;EKKO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MANDT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MANDT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;EKPO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EMATN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EMATNR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Details of View:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Tables: EKKO; EKPO; EKET&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Join Condition relationships on giving the above tables is:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;EKKO&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKPO&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKPO&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKET&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKKO&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKET&lt;/TD&gt;&lt;TD&gt;MANDT&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKKO&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKPO&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKPO&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKET&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKKO&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKET&lt;/TD&gt;&lt;TD&gt;EBELN&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;EKPO&lt;/TD&gt;&lt;TD&gt;EBELP&lt;/TD&gt;&lt;TD&gt;=&lt;/TD&gt;&lt;TD&gt;EKET&lt;/TD&gt;&lt;TD&gt;EBELP&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not able to include MATNR in the Join conditions as only EKPO table is having MATNR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;In most of the programs MATNR field is used in the where clause while fetching the data from match code ID/view. Please suggest how can I improve the performance.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2013 18:47:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576621#M1756113</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-02T18:47:16Z</dc:date>
    </item>
    <item>
      <title>Re: Matchcode replaced with View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576622#M1756114</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;you have complicated your join query. please try this join condition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EKKO EBELN = EKPO EBELN&lt;/P&gt;&lt;P&gt;EKKO EBELN = EKET EBELN&lt;/P&gt;&lt;P&gt;EKPO EBELP = EKET EBELP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or else&lt;/P&gt;&lt;P&gt;if you know how to get data ahead of time from EKKO. Get that and then query EKPO and EKET.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;swanand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2013 19:25:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576622#M1756114</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-02T19:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: Matchcode replaced with View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576623#M1756115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Swanand,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The sequence you have mentioned is atleast saving program from run time error, but still we have performance issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did not get your point: &lt;SPAN style="color: #333333; font-size: 12px; background-color: #ffffff;"&gt;if you know how to get data ahead of time from EKKO. Get that and then query EKPO and EKET.&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: #333333; font-size: 12px; background-color: #ffffff;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-size: 12px; background-color: #ffffff;"&gt;Vachana&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2013 22:08:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576623#M1756115</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-02T22:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: Matchcode replaced with View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576624#M1756116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I meant get the required EBELN from EKKO first and then get the required data from EKPO and EKET. This way you might reduce the performance issue a little more. Join on two table (EKPO and EKET) will be a little better that join on EKKO-EKPO-EKET.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2013 23:50:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/matchcode-replaced-with-view/m-p/9576624#M1756116</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-08-02T23:50:35Z</dc:date>
    </item>
  </channel>
</rss>

