<?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: pooledtables in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736800#M899329</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi ranjana,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data.  Several pooled tables can be cominied in a table pool. The data of these pooled tables are then sorted in a common table in the database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cluster Table :  Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data.  They can also be used to store temporary data or texts, such as documentation. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Pool Tables (match codes, look up tables)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1) Should be accessed via primary key or &lt;/P&gt;&lt;P&gt;2) Should be buffered (SE11-&amp;gt;Display Table-&amp;gt;technical settings) &lt;/P&gt;&lt;P&gt;3) No secondary indexes &lt;/P&gt;&lt;P&gt;Select *  is Ok because all columns retrieved anyway &lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Cluster Tables (BSEG,BSEC)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1) Should be accessed via primary key - very fast retrieval     otherwise very slow &lt;/P&gt;&lt;P&gt;2) No secondary indexes &lt;/P&gt;&lt;P&gt;3) Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required. &lt;/P&gt;&lt;P&gt;4) Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported &lt;/P&gt;&lt;P&gt;5) Can not be buffered &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards ,&lt;/P&gt;&lt;P&gt;sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 26 Apr 2008 13:41:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-26T13:41:07Z</dc:date>
    <item>
      <title>pooledtables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736797#M899326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts !&lt;/P&gt;&lt;P&gt;are pooledtables and cluster tables are used in real scenerio. how i can find  and use pooledtables and cluster tables .&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Apr 2008 13:58:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736797#M899326</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-25T13:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: pooledtables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736798#M899327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Of course an example is table BSEG which is the heart of FI. But we dont select data from it directly. Without BSEG there is no FI at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Apr 2008 14:03:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736798#M899327</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-25T14:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: pooledtables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736799#M899328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ranjana Sharma ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;create a transperant table in SE11 with fields and then before activating &lt;/P&gt;&lt;P&gt;Goto Extras--&amp;gt;Change table category and select pooled or cluster table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They Are used in real scenarios ,Check BSEG table used in FI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THanks ,&lt;/P&gt;&lt;P&gt;Surya Pydikondala.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Apr 2008 16:46:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736799#M899328</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-25T16:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: pooledtables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736800#M899329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi ranjana,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data.  Several pooled tables can be cominied in a table pool. The data of these pooled tables are then sorted in a common table in the database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cluster Table :  Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data.  They can also be used to store temporary data or texts, such as documentation. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Pool Tables (match codes, look up tables)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1) Should be accessed via primary key or &lt;/P&gt;&lt;P&gt;2) Should be buffered (SE11-&amp;gt;Display Table-&amp;gt;technical settings) &lt;/P&gt;&lt;P&gt;3) No secondary indexes &lt;/P&gt;&lt;P&gt;Select *  is Ok because all columns retrieved anyway &lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Cluster Tables (BSEG,BSEC)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1) Should be accessed via primary key - very fast retrieval     otherwise very slow &lt;/P&gt;&lt;P&gt;2) No secondary indexes &lt;/P&gt;&lt;P&gt;3) Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required. &lt;/P&gt;&lt;P&gt;4) Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported &lt;/P&gt;&lt;P&gt;5) Can not be buffered &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards ,&lt;/P&gt;&lt;P&gt;sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Apr 2008 13:41:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/pooledtables/m-p/3736800#M899329</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-26T13:41:07Z</dc:date>
    </item>
  </channel>
</rss>

