Solved: hi friends,

Former Member · ‎07-11-2007

can anyone please tell me the difference between transperant tables,cluster tables and pooled tables.

which table we will be using frequently n what is the use?

Former Member · ‎07-11-2007

transparent tables are which we actually use, these tables will have one to one relation with database. pooled tables and cluster are system tables, generally we dont use them.

pooled tables hold control data like screen sequences, and cluster table hold documentation data.

Former Member · ‎07-11-2007

transparent tables are which we actually use, these tables will have one to one relation with database. pooled tables and cluster are system tables, generally we dont use them.

pooled tables hold control data like screen sequences, and cluster table hold documentation data.

Former Member · ‎07-11-2007

Hi

The following are the table types used in SAP :

I. Transparent tables (BKPF, VBAK, VBAP, KNA1, COEP)

Allows secondary indexes (SE11->Display Table->Indexes)

Can be buffered (SE11->Display Table->technical settings) Heavily updated tables should not be buffered.

II. Pool Tables (match codes, look up tables)

Should be accessed via primary key or

Should be buffered (SE11->Display Table->technical settings)

No secondary indexes

Select * is Ok because all columns retrieved anyway

III. Cluster Tables (BSEG,BSEC)

Should be accessed via primary key - very fast retrieval otherwise very slow

No secondary indexes

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.

Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported

Can not be buffered

IV. Buffered Tables (includes both Transparent & Pool Tables)

While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.

Reward points if useful

Regards

Ashu

Former Member · ‎07-11-2007

Hi,

Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

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.

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.

Also refer this…

http://help.sap.com/saphelp_nw04/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm

***do rewards if usefull

vijay

Former Member · ‎07-11-2007

Hi,

Transparent tables are much more common than pooled or cluster tables. They are used to hold application data. Application data is the master data or transaction data used by an application. An example of master data is the table of vendors (called vendor master data), or the table of customers (called customer master data). An example of transaction data is the orders placed by the customers, or the orders sent to the vendors.

A pooled table in R/3 has a many-to-one relationship with a table in the database.For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.However, in the database, it is stored along with other pooled tables in a single table called a table pool.R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each).

A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. 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.

Hope this helps.

Reward if helpful.

Regards,

Sipra

Former Member · ‎07-11-2007

Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

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.

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.

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.

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.

A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.

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.

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.

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.

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.

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.

A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.

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.

Reward points if helpful

Former Member · ‎07-11-2007

hi,

Transparent Table:

Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

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.

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.

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.

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.

A clustered and a pooled table cannot be read from outside SAP

because certain data are clustered and pooled in one field.

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.

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.

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.

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.

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.

A structure is a table without data.

It is only filled by program logic at the moment it is needed starting from tables.

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.

Transparent table:

Tables can be defined independently of the database in the ABAP Dictionary.

The fields of the table are defined together with their (database-independent) data types and lengths.

A table definition in the ABAP Dictionary has the following components:

Table fields: The field names and the data types of the fields contained in the table are defined here.

Foreign keys: The foreign keys define the relationships between this table and other tables.

Technical settings: The technical settings define how the table is created on the database.

Indexes: Indexes can be defined for the table to speed up data selection from the table.

There are three categories of database tables in the ABAP Dictionary.

A physical table definition is created in the database for the table definition stored

in the ABAP Dictionary for transparent tables when the table is activated.

The table definition is translated from the ABAP Dictionary to a definition of the particular database.

On the other hand, pooled tables and cluster tables are not created in the database.

The data of these tables is stored in the corresponding table pool or table cluster.

It is not necessary to create indexes and technical settings for pooled and cluster tables.

Pooled table

Pooled tables can be used to store control data

(e.g. screen sequences, program parameters or temporary data)..

Several pooled tables can be combined to form a table pool.

The table pool corresponds to a physical table on the database in which all the records of the

allocated pooled tables are stored.

Cluster table

Cluster tables contain continuous text, for example, documentation.

Several cluster tables can be combined to form a table cluster.

Several logical lines of different tables are combined to form a physical record in this table type.

This permits object-by-object storage or object-by-object access.

In order to combine tables in clusters, at least parts of the keys must agree.

Several cluster tables are stored in one corresponding table on the database.

Regards

Reshma

Former Member · ‎07-11-2007

Hi

1st let me explain what are different types of tables

Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

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.

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.

Here comes the difference between those tables