Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
transperent tables have one to one relation ship ie., the structure which defined in the data dictionary level(here we define the tables etc..) is same as in database level(here the data is stored physically).we usually create transperent tables only.
In cluster and pooled tables they have many to one relationship ie., they have many structuresor defnitions at dictionary level but a single table in database level.
the major difference is cluster tables must have at least one primary key common but in pooled they may have or may not have a primary key in common.
usually we dont create any cluster and pooled tables because they are in proprietry format of SAP.
transperent tables have one to one relation ship ie., the structure which defined in the data dictionary level(here we define the tables etc..) is same as in database level(here the data is stored physically).we usually create transperent tables only.
In cluster and pooled tables they have many to one relationship ie., they have many structuresor defnitions at dictionary level but a single table in database level.
the major difference is cluster tables must have at least one primary key common but in pooled they may have or may not have a primary key in common.
usually we dont create any cluster and pooled tables because they are in proprietry format of SAP.
Both are table types , the major difference b/w cluster table and pooled tables are
cluster table and pooled tables are having cardinality ratio is M:N and pooled tables are contains all the primary key field of the table , pooled tables are used to store the system 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.
here is the basic difference b/t both the tables ....
Pool Tables
1) Many to One Relationship.
2) Table in the Dictionary has the different name, different number of fields, and the fields have the different name as in the R3 Table definition.
3) It can hold only pooled tables.
cluster Tables:
1) These are logical tables that are arranged as records of transparent tables.
2) One cannot use Native SQL on these tables (only Open SQL).
3) They are not manageable directly using database system tools.
These two table are used to store system data and onother for configural data.
if u want to fetch the data from DB table u need to go for trasperent tables only.
Bcoz transperent tables are one - one relation.
Bluesky
