Cluster table defination not as per book give me own defination

Hi gurus,
Please give me the cluster table defination and how to create it step by step method.
Dont give answer Tables assigned to a table cluster are referred to as cluster tables.
I know that give explanation what is the need of this tables already there is database tables. why we need to create cluster tables? how to retrive the data and how we maintained those cluster tables in data dictionary
Thanks,
Harikiran
Edited by: harikiran mitnala on Jul 14, 2008 11:02 PM
Edited by: harikiran mitnala on Jul 14, 2008 11:05 PM

Hi Hari,
1. Cluster tables combine the data from several tables with
   identical (or almost identical) keys into one physical record
   on the database.
2. Data is written to a database in compressed form.
3.    Retrieval of data is very fast if the primary key is known.
4.. Cluster tables are defined in the data dictionary as transparent tables.
5. External programs can NOT interpret the data in a cluster table.
6. Special language elements EXPORT TO DATABASE, IMPORT TO DATABASE and DELETE FROM DATABASE are used to process data in the cluster tables.
Hope this helps you.
Regards,
Chandra Sekhar

Similar Messages

Customer Defined Data Classes on Cluster Tables?

Hi all,
I noticed that there is no option within db13 to change the storage option to a customer defined data class, for cluster tables. I am sure this is by design but wanted to check to see if anyone has had any luck defining a data class on a cluster table.
We could move a cluster table to a DB2 tablespace and define the new Data Class through dbacockpit/db02, but there is no option to change the data class definition in the data dictionary (se13) to use the new Data Class for the table itself.
Mainly what we are aiming for is to be able to move 2 tables into their own tablespaces on the target server, during a migration. Sapinst is looking at the Data Classes to create DDLDB6.XML, which defines the tablespace assignments to the target server, so perhaps there is a preferred method of making this change, if it does exist.
Thanks for any insights,
Derek

Hi guys,
Thanks for the helpful answers. I should add some more detail.
Our tablespaces have already been moved to new tablespaces on the source system, with DB6CONV, and we have updated our data classes through db02, with no problems. So sapinst uses the data class definitions to create the custom tablespaces, and then uses the data class assignments to assign the table to a tablespace.
However, the cluster tables do not seem to support the data class assignment in se13, the option is not available as it is for normal tables. Let me see if I can post a screenshot somewhere with a cluster table versus a normal table. For example, there is no option to change the data class for table CDCLS in se13.
I am wondering if this is a limitation of the version of R/3 we are using, or if the limitation for cluster tables is something that is intended on all versions of R/3.
If we can't use db13 to make the assignment, we may try the custom definition in the STR file as Kiran mentioned.

Pool table & Cluster table

Dear all,
could you please help me out from the below.
How to create pooled tables & cluster tables.
When i am trying to create a table, by default it is showing table category as Transparent table.
Regards
Venkat

hi,
A pool table has many to one relation with the table in the database. For one table in the database there are many tables in the dictionary. Tha table in the database has a diff name than in the table in the data dict, it has diff no of fields and field names are different. A pooled table is stored in the pool at the database level. A table pool is a databse table with a special struct that enables the data of many R3 tables to be stored in it. It can hold only pooled tables
Cluster table are logical tables that must be assigned to a table cluster when they are defined.
Cluster table can be used to store control data they can also used to store temporary data or text such as documentation
Pool table
A database table defined in the ABAP Dictionary whose database instance is assigned to more than one table defined in the ABAP Dictionary. Multiple pool tables are assigned to a table pool in the database. The key fields of a pool table have to be character-type fields. The table pool's primary key consists of two fields: TABNAME for the name of a pool table, and VARKEY for the interdependent contents of the key fields in the corresponding pool table. The non-key fields of the pool table are stored in compressed format in their own column, called VARDATA, of the table pool. The only way to access pool tables is by using Open SQL. Joins are not allowed.
Table Pool
Database table in the database that contains the data of several pool tables.
Cluster Table
Database table defined in the ABAP Dictionary, whose version on the database is not only assigned to one table defined in the ABAP Dictionary. Several cluster tables are assigned to a table cluster in the database. The intersection of the key fields of the cluster tables forms the primary key of the table cluster. The other columns of the cluster tables are stored in compressed form in a single column VARDATA of the table cluster. You can access cluster tables only via Open SQL, and only without using joins.
Table Cluster
Database table in the database that contains the data of several cluster tables.
Note: Never mix up with a database table that has the necessary structure for storing data clusters in database tables and in the shared memory. Those are called INDX-type, with reference to the database table INDX supplied by SAP. Data clusters are groupings of data objects for transient and persistent storage in a selectable storage medium. A data cluster can be processed using the statements IMPORT, EXPORT, and DELETE FROM
Some pooled tables:
T000 Clients
T000C Table for Installing FI-SL Customizing
T000CM Client-specific FI-AR-CR settings
T000F Cross-Client FI Settings
T000G Cross-Client FI-SL Postings
T000GL Flexible general ledger: Customizing check
T000K Group
T000MD MRP at MRP Area Level
T001 Company Codes
T001_ARCH Archive contents short description
T001_CONV Company codes affected by currency convers
T001A Additional Local Currencies Control for Co
T001B Permitted Posting Periods
T001C Valid Posting Periods for Global Companies
T001CM Permitted Credit Control Areas per Company
T001D Validation of Accounting Documents
T001E Company Code-Dependent Address Data
T001F Company code-dependent form selection
T001G Company Code-Dependent Standard Texts
T001I Company Code - Parameter Types
T001J Company Code - Parameter Type Names
T001K Valuation area
T001L Storage Locations
T001M Data on Z5A Foreign Trade Regulations Repo
T001N Company Code - EC Tax Numbers / Notificati
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.
regards,
pritha

What is the differences between Transparent,Pooled and Cluster tables?

Hello all,
What is Pool table?What is the differences between Transparent,Pooled and Cluster tables?
Regards!
Purna

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.
Regds,
Manohar

Can we create secondary index for a cluster table

hi
can we create secondary index for a cluster table

Jyothsna,
There seems to be some kind of misunderstanding here. You cannot create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).
Hope this clarifies things,
Mark

Generic extractors on pool table and Cluster tables

Good Afternoon all,
Can we create generic extractors on Cluster or pool Table. If yes Let me know how?
I am trying to create a Generic Extractor on BSEC Table but it is not allowing me to do this. It throws error that"Extraction from pool tables and cluster tables is not permitted"
Kindly guide me on this
Thanks,
Vaishali.

Hi
you cannot do generic extraction directly on pooled or cluster tables.
You can create a function module, then you can create a Generic Data source based on this..
Hope it helps,
Thanks,
Teja
Edited by: Teja badugu on Apr 15, 2008 12:24 PM

How many SECONDARY INDEXES are created for CLUSTER TABLES?

how many SECONDARY INDEXES are created for CLUSTER TABLES?
please explain.

There seems to be some kind of misunderstanding here. You cannot create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).

Why Inner join or Outer join is not used for Pool or Cluster tables ?

Hi SAP-ABAP Experts .
With Due Regards .
May u explain me why Inner join or Outer join is not useful for Pool or Cluster tables ?
because peoples advised not use Joins for Pool and Cluster tables , What harm will take place , If we do this ?
Best Regards to all : Rajneesh

Both Pooled and Cluster Tables are stored as tables within the database. Only the structures of the two table types which represent a single logical view of the data are defined within the ABAP/4 Data Dictionary. The data is actually stored in bulk storage in a different structure. These tables are commonly loaded into memory (i.e., 'buffered') due to the fact they are typically used for storing internal control information and other types of data with little or no external (business) relevance.
Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
Secondary indexes cannot be created.
You cannot use the ABAP/4 constructs select distinct or group by.
You cannot use native SQL.
You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
I hope it helps.
Best Regards,
Vibha
Please mark all the helpful answers

How to read data from a CLUSTER STRUCTURE not cluster table.

Hi,
how to read data from a CLUSTER STRUCTURE not cluster table.
regards,
Usha.

Hello,
A structre doesnt contain data.. so u cannot read from it. U need to find out table of that structure and read data from it.
Regards,
Mansi.

My mac book gives electric shock through its entire body while being charged from AC out let. is there a solution to the problem? my other two friends are haveing the same problem who recently have purchased the same note books, its weird for APPLE

My mac book gives electric shock through its entire body while being charged from AC out let. is there a solution to the problem? my other two friends are haveing the same problem who recently have purchased the same note books, its weird for APPLE products. Please give any solution.

Is the MBP properly grounded? Are you using the three prong plug? If not, do so and your problems may disappear. If not, do what SwankPeRFection suggests.
Ciao.

I do not recieve texts from iMessage friends when I am not connected to the internet(wifi nor 3G). Am I supposed to, if so is there a setting on my part to fix this? Even the techs at my provider can not give me a definative answer.

I do not recieve texts from iMessage friends when I am not connected to the internet(wifi nor 3G). Am I supposed to, if so is there a setting on my part to fix this? Even the techs at my provider can not give me a definative answer.

iMessage uses data not your messaging plan. You need to have either Wi-Fi or cellular data turned on to use iMessage

Table type not defined for table control "T_CONTROL" (Custom table)

Hi All,
I m facing a problem in ITS mobile service.
The Table control designed by me in R/3 (Module pool program) is
not getting displayed in ITS mobile page.
It is giving me an error "Table type not defined for table control "T_CONTROL" (Custom table) ".
Can you please let me how this issue can be resolved.
With Regards,
Mahesh

CONTROLS: table_ctr TYPE TABLEVIEW USING SCREEN '0010'.
try using this....
Regards
Vasu

Define view for cluster table?

Hi Experts,
Can we create a database view with a cluster table? Please let me know how.
Regards,
Vishal.

Hi,
Please try this and use BSEG as an example.
1. Go to SE12.
2. Enter BSEG
3. Click Display button
4. Go to Delivery and Maintenance' tab.
5. You should be able to see Pool/cluster RFBLG.
6. Double click RFBLG and then click Where-Used list button (CTRLSHIFTF3).
7. Select Table option and click Execute button.
8. System will show all the table that belong to this pool/cluster.
For Pool/Cluster REGUC, it is only used in table REGUP.
Regards,
Ferry Lianto

Hash Cluster Tables vs Partitioning

Hi All,
Can we create partition on Cluster tables?
As per understanding Cluster can give excellent performance if used carefully, in our case we need to purge our data also.
We can purge the partitions easly.
Can you help me for the comparion of these two objects?
Thanks
Sandeep

No , Oracle does not support this.
http://download.oracle.com/docs/cd/B28359_01/server.111/b32024.pdf (page 4-19).
The rules for partitioning indexes are similar to those for tables:
■ An index can be partitioned unless:
– The index is a cluster index.
– The index is defined on a clustered table
Thanks
http://swervedba.wordpress.com/

Doubt in Cluster table

Hi Experts,
Can You plz tell How to import/read data from cluster table? Plz give me the syntaxes also..
Thanx in advance.

use read statement i don't think in cluster table there is any restruction for read and select u can use open sql but not join in cluster table .
Database table defined in the ABAP Dictionary, whose version on the database is not only assigned to one table defined in the ABAP Dictionary. Several cluster tables are assigned to a table cluster in the database. The intersection of the key fields of the cluster tables forms the primary key of the table cluster. The other columns of the cluster tables are stored in compressed form in a single column VARDATA of the table cluster. You can access cluster tables only via Open SQL, and only without using joins.

Cluster table defination not as per book give me own defination

Similar Messages

Maybe you are looking for