<?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: FBRA performance issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613350#M1087015</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;The issue has been solved after creating the index in database.&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Feb 2009 04:52:54 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-02-05T04:52:54Z</dc:date>
    <item>
      <title>FBRA performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613348#M1087013</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;We have an performance issue with FBRA t-code which uses the BKORM table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can the building of an index to this table will imporve the performance? How about the buffering of the table?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, provide us the difference between unique and non unique index types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;DVRK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2008 06:18:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613348#M1087013</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-10-14T06:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: FBRA performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613349#M1087014</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; We have an performance issue with FBRA t-code which uses the BKORM table.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Can the building of an index to this table will imporve the performance? How about the buffering of the table?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard transaction, check in SAP Service Marketplace for possible fixes. Don't switch on buffering for such a potentially large table with frequent changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Also, provide us the difference between unique and non unique index types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This you can find out yourself with a little research effort.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2008 07:23:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613349#M1087014</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2008-10-14T07:23:42Z</dc:date>
    </item>
    <item>
      <title>Re: FBRA performance issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613350#M1087015</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;The issue has been solved after creating the index in database.&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Feb 2009 04:52:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/fbra-performance-issue/m-p/4613350#M1087015</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-05T04:52:54Z</dc:date>
    </item>
  </channel>
</rss>

