<?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 Issues while executing LT27 transaction in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773043#M646203</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do a performance trace and see if it is using any index. It looks like it shoould use index LTAP~M.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Sep 2007 14:32:44 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-11T14:32:44Z</dc:date>
    <item>
      <title>Performance Issues while executing LT27 transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773042#M646202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are getting a 'Time Out' error while executing the transaction LT27. The reason for this is an expensive select statement on LTAP in the standard code given below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    select * from LTAP appending table iltap&lt;/P&gt;&lt;P&gt;             where     nlenr eq lagerein&lt;/P&gt;&lt;P&gt;             and       lgnum eq lagernum&lt;/P&gt;&lt;P&gt;             and       pquit eq con_x&lt;/P&gt;&lt;P&gt;             and       kzsub in kzsub_tab&lt;/P&gt;&lt;P&gt;             and       (DS_clauses-where_tab)&lt;/P&gt;&lt;P&gt;             %_HINTS&lt;/P&gt;&lt;P&gt;                DB2 '&amp;amp;SUBSTITUTE LITERALS&amp;amp;'&lt;/P&gt;&lt;P&gt;                DB6 '&amp;amp;SUBSTITUTE LITERALS&amp;amp;'&lt;/P&gt;&lt;P&gt;                ORACLE '&amp;amp;SUBSTITUTE LITERALS&amp;amp;'&lt;/P&gt;&lt;P&gt;                MSSQLNT '&amp;amp;SUBSTITUTE LITERALS&amp;amp;'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One possibe solution for this is to create a secondary index on NLENR field but we want to avoid that because we already have 5 secondary Indices on LTAP. We already implemented the SAP note 999743 but it was of no use. Please reply ASAP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 14:11:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773042#M646202</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T14:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issues while executing LT27 transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773043#M646203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do a performance trace and see if it is using any index. It looks like it shoould use index LTAP~M.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 14:32:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773043#M646203</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T14:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issues while executing LT27 transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773044#M646204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your response Rob. I did run the SQL trace for the transaction  and it was pointing to one of the custom Index that we created. We decided not to go ahead with the Index creation anymore because the performance increases remarkably when we add additional selection criteria by checking the Additional selections box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Sep 2007 15:56:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773044#M646204</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-13T15:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issues while executing LT27 transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773045#M646205</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arun,&lt;/P&gt;&lt;P&gt;We are facing the same peroformance issue with LT27 . To overcome it we created a secondary index in table LTAP , already there are 5 indexes in table LTAP , its performance improved a lot , but it effected the performance of LT22 which uses the same table LTAP. We wanted to know more how you got resolved the issue by creating an additional selection criteria.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I shall  be thankful for you , if you can recall  the issue and respond.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Vengal Rao.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Nov 2009 15:05:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues-while-executing-lt27-transaction/m-p/2773045#M646205</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-30T15:05:17Z</dc:date>
    </item>
  </channel>
</rss>

