<?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: table type in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481429#M836954</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;i)Transparent tables - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.   Both Opensql and Nativesql can be used. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ii)Pool tables &amp;amp; iii)Cluster tables -  &lt;/P&gt;&lt;P&gt;These are logical tables that are arranged as records of transparent tables.one cannot use native sql on these tables &lt;/P&gt;&lt;P&gt;(only opensql).They are not managable directly using database system tools. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transparent Table :  Exists with the same structure both in dictionary as well as in database  exactly with the same data and fields. &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;A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10)  cluster table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Mar 2008 05:45:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-04T05:45:05Z</dc:date>
    <item>
      <title>table type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481426#M836951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;plz define transparent table , pool table and cluster table with example&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Mar 2008 16:03:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481426#M836951</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-03T16:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: table type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481427#M836952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Agarwal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.Transparent Tables&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;             &amp;#149;A transparent table in the dictionary has a one-to-one relationship with a table in the database.&lt;/P&gt;&lt;P&gt;             &amp;#149;Its structure in R/3 Data Dictionary corresponds to a single database table.&lt;/P&gt;&lt;P&gt;             &amp;#149;Transparent tables are much more common than pooled or cluster tables.&lt;/P&gt;&lt;P&gt;             &amp;#149;They are used to hold application data.&lt;/P&gt;&lt;P&gt;             &amp;#149; Application data is the master data or transaction data used by an application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2.Table Pools and Pooled Table&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;             &amp;#149;	Pooled table in R/3 has a many-to-one relationship with a table in the database.&lt;/P&gt;&lt;P&gt;             &amp;#149;	For one table in the database, there are many tables in the R/3 Data Dictionary.&lt;/P&gt;&lt;P&gt;             &amp;#149;	When you look at a pooled table in R/3, you see a description of a table.&lt;/P&gt;&lt;P&gt;             &amp;#149;	 However, in the database, it is stored along with other pooled tables in a single table called a table pool.&lt;/P&gt;&lt;P&gt;             &amp;#149;	A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. &lt;/P&gt;&lt;P&gt;             &amp;#149;	It can only hold pooled tables.&lt;/P&gt;&lt;P&gt;             &amp;#149;	R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each).&lt;/P&gt;&lt;P&gt;             &amp;#149;	Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. &lt;/P&gt;&lt;P&gt;             &amp;#149;	SAP uses them for system data.&lt;/P&gt;&lt;P&gt;             &amp;#149;	Pooled tables are primarily used by SAP to hold customizing data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3.Table Cluster and Cluster Table&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;             &amp;#149;	A cluster table is similar to a pooled table.&lt;/P&gt;&lt;P&gt;             &amp;#149;	 It has a many-to-one relationship with a table in the database.&lt;/P&gt;&lt;P&gt;             &amp;#149;	 Many cluster tables are stored in a single table in the database called a table cluster. &lt;/P&gt;&lt;P&gt;             &amp;#149;	A table cluster is similar to a table pool. &lt;/P&gt;&lt;P&gt;             &amp;#149;	It holds many tables within it.&lt;/P&gt;&lt;P&gt;             &amp;#149;	The tables it holds are all cluster tables. &lt;/P&gt;&lt;P&gt;             &amp;#149;	Like pooled tables, cluster tables are another proprietary SAP construct.&lt;/P&gt;&lt;P&gt;             &amp;#149;	 They are used to hold data from a few (approximately 2 to 10) very large tables.&lt;/P&gt;&lt;P&gt;             &amp;#149;	They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Restrictions on Pooled and Cluster Tables&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;             &amp;#149;	Pooled and cluster tables are usually used only by SAP and not used by customers.&lt;/P&gt;&lt;P&gt;             &amp;#149;	Secondary indexes cannot be created. &lt;/P&gt;&lt;P&gt;             &amp;#149;	You cannot use the ABAP/4 constructs select distinct or group by. &lt;/P&gt;&lt;P&gt;             &amp;#149;	You cannot use native SQL.&lt;/P&gt;&lt;P&gt;             &amp;#149;	You cannot specify field names after the order by clause. &lt;/P&gt;&lt;P&gt;             &amp;#149;	Order by primary key is the only permitted variation. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Harish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Mar 2008 05:41:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481427#M836952</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-04T05:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: table type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481428#M836953</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields. &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;difference between Standard tables, Pooled tables and Clusterd Tables&lt;/P&gt;&lt;P&gt;A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10) cluster table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Mar 2008 05:44:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481428#M836953</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-04T05:44:50Z</dc:date>
    </item>
    <item>
      <title>Re: table type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481429#M836954</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI&lt;/P&gt;&lt;P&gt;i)Transparent tables - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.   Both Opensql and Nativesql can be used. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ii)Pool tables &amp;amp; iii)Cluster tables -  &lt;/P&gt;&lt;P&gt;These are logical tables that are arranged as records of transparent tables.one cannot use native sql on these tables &lt;/P&gt;&lt;P&gt;(only opensql).They are not managable directly using database system tools. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transparent Table :  Exists with the same structure both in dictionary as well as in database  exactly with the same data and fields. &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;A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10)  cluster table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Mar 2008 05:45:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481429#M836954</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-04T05:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: table type</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481430#M836955</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;TABLE TYPES:&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="----------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRANSPARENT TABLES:&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; These type of tables have one to one relationship with the underlying database table. The structure of this table will be in the form of rows and columns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MASTER AND TRANSACTION DATAS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;POOLED TABLE: &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Several pooled tables in data dictionary are stored under one table pool in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLUSTER TABLE:&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Several cluster tables in data dictionary are stored under one table cluster in the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The difference between pooled table and cluster table is in the form of storage of datas.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Several pooled table records are stored in one table pool in the database in continuous format using a row separator. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whereas in the case of table cluster, the records are stored in continuous format without any row separator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES CLASSIFICATION BASED ON CLIENT:&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLIENT-DEPENDENT TABLE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLIENT-INDEPENDENT TABLE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES CLASSIFICATION BASED ON BUFFERING:&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SINGLE RECORD BUFFERING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GENERIC BUFFERING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FULLY BUFFERED.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Mar 2008 05:49:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-type/m-p/3481430#M836955</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-04T05:49:41Z</dc:date>
    </item>
  </channel>
</rss>

