<?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: Performance - table LTAP in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521921#M1560591</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would start by making sure that the statistcs are up to date. The table key should definitely be selected by the optimizer for that access.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Dec 2010 18:13:32 GMT</pubDate>
    <dc:creator>Rui_Dantas</dc:creator>
    <dc:date>2010-12-02T18:13:32Z</dc:date>
    <item>
      <title>Performance - table LTAP</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521919#M1560589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAP 4.7 6.20 ORACLE 10G  WINDOWS SERVER 2008&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have several selects to table LTAB which seem to be very slow.&lt;/P&gt;&lt;P&gt;The clause of this select is : where MANDT = A0 and LGNUM = A1 and TANUM in (A2, A3, A4, A5, A6).&lt;/P&gt;&lt;P&gt;In sm66 it's in sequential read, and in st04 it's using INDEX RANGE SCAN LTAP~M which is an SAP index.&lt;/P&gt;&lt;P&gt;This index is by : MANDT, LGNUM, PQUIT, MATNR.&lt;/P&gt;&lt;P&gt;And the slow programs are standard.&lt;/P&gt;&lt;P&gt;But the keys of the table are : MANDT, LGNUM, TANUM, TAPOS, so I don't understand why it's using the index instead of reading by the own table.&lt;/P&gt;&lt;P&gt;Sometimes I see in sm66 4, 5 programs accessing this table with this select at the same time, and it takes some time for them to disappear.&lt;/P&gt;&lt;P&gt;And I don't understand why.&lt;/P&gt;&lt;P&gt;Does anybody have a clue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eduardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 15:25:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521919#M1560589</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-12-02T15:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Performance - table LTAP</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521920#M1560590</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;SAP Note 191492 - Performance: Customer developments in MM/WM has a question about this table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the problem is in an standard report, search notes, surely it's an error or performance note. It's sure if you have applied recently support-packages or you are using this functionality since a recent time. If you don't find it, send a message to SAP. Check  Note 67739 - Priorities of problem messages.&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;Eduardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 15:39:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521920#M1560590</guid>
      <dc:creator>eduardo_hinojosa</dc:creator>
      <dc:date>2010-12-02T15:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Performance - table LTAP</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521921#M1560591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would start by making sure that the statistcs are up to date. The table key should definitely be selected by the optimizer for that access.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 18:13:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-table-ltap/m-p/7521921#M1560591</guid>
      <dc:creator>Rui_Dantas</dc:creator>
      <dc:date>2010-12-02T18:13:32Z</dc:date>
    </item>
  </channel>
</rss>

