<?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: MSEG Table performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/mseg-table-performance-issue/m-p/407029#M10615</link>
    <description>&lt;P&gt;I hope you have checked that the internal table used in the FOR ALL ENTRIES clause is not empty. &lt;/P&gt;&lt;P&gt;Do you have the possibility to either&lt;/P&gt;&lt;UL&gt;
&lt;LI&gt;Replace the FOR ALL ENTRIES with a JOIN or a SUBQUERY with the query that extracted the list of item numbers&lt;/LI&gt;&lt;LI&gt;Split the list of items into smaller packages and either execute them in sequence (better use of memory) or in parallel (Select data in a RFC FM called DESTINATION 'NONE').&lt;/LI&gt;&lt;LI&gt;Check with basis for performance of FOR ALL ENTRIES (&lt;A href="https://launchpad.support.sap.com/#/notes/772497"&gt;Oracle hints&lt;/A&gt; in emergency situations) such as system parameters : rsdb/max_blocking_factor, rsdb/max_in_blocking_factor, rsdb/prefer_join, rsdb/prefer_union_all.&lt;/LI&gt;&lt;LI&gt;Check if index MSEG~BUD is active and statistics up-to-date&lt;/LI&gt;&lt;LI&gt;In very rare situations (many report have problems) creation of specific indexes. &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Does your organization consider upgrading Oracle version, what's your SAP version ?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2020 08:24:39 GMT</pubDate>
    <dc:creator>RaymondGiuseppi</dc:creator>
    <dc:date>2020-10-15T08:24:39Z</dc:date>
    <item>
      <title>MSEG Table performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mseg-table-performance-issue/m-p/407028#M10614</link>
      <description>&lt;P&gt;hi Team,&lt;/P&gt;
  &lt;P&gt;We have 640 GB size of MSEG table running on oracle 11g database.&lt;/P&gt;
  &lt;P&gt;But this is taking longer time in fetch and having slow performance.Below is the SQL query being used in program&lt;/P&gt;
  &lt;P&gt;SELECT mjahr mblnr zeile budat_mkpf vgart_mkpf &lt;BR /&gt; werks lgort kokrs kostl &lt;BR /&gt; matnr bwart grund menge &lt;BR /&gt; meins dmbtr waers "SAP-5367&lt;BR /&gt; APPENDING CORRESPONDING FIELDS OF TABLE t_docitems &lt;BR /&gt; FROM mseg &lt;BR /&gt; FOR ALL ENTRIES IN it_matnrpack &lt;BR /&gt; WHERE matnr = it_matnrpack-matnr &lt;BR /&gt; AND budat_mkpf EQ wa_budmat-budat &lt;BR /&gt; AND werks EQ p_werks &lt;BR /&gt; AND bwart IN s_bwart &lt;BR /&gt; AND lgort IN s_lgort &lt;BR /&gt; AND kostl IN s_kostl. &lt;/P&gt;
  &lt;P&gt; Index is being used in this query but having fileds MANDT,MATNR,WERKS,GRUND and LIFNR.&lt;/P&gt;
  &lt;P&gt; Please suggest if any improvements is there which can be improve performance.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2017 18:05:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mseg-table-performance-issue/m-p/407028#M10614</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-07-14T18:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: MSEG Table performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mseg-table-performance-issue/m-p/407029#M10615</link>
      <description>&lt;P&gt;I hope you have checked that the internal table used in the FOR ALL ENTRIES clause is not empty. &lt;/P&gt;&lt;P&gt;Do you have the possibility to either&lt;/P&gt;&lt;UL&gt;
&lt;LI&gt;Replace the FOR ALL ENTRIES with a JOIN or a SUBQUERY with the query that extracted the list of item numbers&lt;/LI&gt;&lt;LI&gt;Split the list of items into smaller packages and either execute them in sequence (better use of memory) or in parallel (Select data in a RFC FM called DESTINATION 'NONE').&lt;/LI&gt;&lt;LI&gt;Check with basis for performance of FOR ALL ENTRIES (&lt;A href="https://launchpad.support.sap.com/#/notes/772497"&gt;Oracle hints&lt;/A&gt; in emergency situations) such as system parameters : rsdb/max_blocking_factor, rsdb/max_in_blocking_factor, rsdb/prefer_join, rsdb/prefer_union_all.&lt;/LI&gt;&lt;LI&gt;Check if index MSEG~BUD is active and statistics up-to-date&lt;/LI&gt;&lt;LI&gt;In very rare situations (many report have problems) creation of specific indexes. &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Does your organization consider upgrading Oracle version, what's your SAP version ?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2020 08:24:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mseg-table-performance-issue/m-p/407029#M10615</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2020-10-15T08:24:39Z</dc:date>
    </item>
  </channel>
</rss>

