Skip to Content
author's profile photo Former Member
Former Member

pooled and cluster tables

plz tell me examples for pooled and cluster tables.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2006 at 04:44 AM

    2) T040, T040A--pooled

    3) BSEG, BSES---->cluster

    or u can serch in se11

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2006 at 04:50 AM

    Go to se11

    table DD02L-> Give TABCLASS as POOL or CLUSTER you will get a list of tables

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2006 at 04:51 AM

    in SE11 , goto table DD02L , there one field will be there to differentiate types of tables , u can filter on that i guess the field description is object class

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2006 at 05:06 AM

    Hi,

    Pooled and Cluster Tables

    Table pools (pools) and table clusters (clusters) are special table types in the ABAP Dictionary. The data from several different tables can be stored together in a table pool or table cluster. Tables assigned to a table pool or table cluster are referred to as pooled tables or cluster tables.

    A table pool or table cluster should be used exclusively for storing internal control information (screen sequences, program parameters, temporary data, continuous texts such as documentation). Data of commercial relevance is usually stored in transparent tables.

    Table Pools

    A table in the database in which all records from the pooled tables assigned to the table pool are stored corresponds to a table pool.

    The definition of a pool consists essentially of two key fields (Tabname and Varkey) and a long argument field (Vardata). A pool has the following structure:

    Field

    Data type

    Meaning

    Tabname

    CHAR(10)

    Name of pooled table

    Varkey

    CHAR (n)

    Contains the entries from all key fields of the pooled table record as a string, max. length for n is 110

    Dataln

    INT2(5)

    Length of the string in Vardata

    Vardata

    RAW (n)

    Contains the entries from all data fields of the pooled table record as a string, max. length n depends on the database system used

    If a pooled table record is saved, it is stored in the table pool assigned. The name of the pooled table is written to the field Tabname. The contents of all key fields of the pooled table are written as a string to field Varkey and the contents of all data fields as a string to field Vardata. The length of the string stored in Vardata is entered in field Dataln by the database interface.

    Due to the structure of a table pool, there are certain restrictions on the pooled tables assigned to it. The name of a pooled table may not exceed 10 characters. Since Varkey is a character field, all key fields of a pooled table must have character data types (for example, CHAR, NUMC, CLNT). The total length of all key fields or all data fields of a pooled table must not exceed the length of the Varkey or Vardata field of the assigned pool.

    Table Clusters

    Several logical data records from different cluster tables can be stored together in one physical record in a table cluster.

    A cluster key consists of a series of freely definable key fields and a field (Pageno) for distinguishing continuation records. A cluster also contains a long field (Vardata) that contains the contents of the data fields of the cluster tables for this key. If the data does not fit into the long field, continuation records are created. Control information on the structure of the data string is still written at the beginning of the Vardata field. A table cluster has the following structure:

    Field

    Data type

    Meaning

    CLKEY1

    *

    First key field

    CLKEY2

    *

    Second key field

    ...

    ...

    ...

    CLKEYn

    *

    nth key field

    Pageno

    INT2(5)

    Number of the continuation record

    Timestamp

    CHAR(14)

    Time stamps

    Pagelg

    INT2(5)

    Length of the string in Vardata

    Vardata

    RAW (n)

    Contains the entries from the data fields of the assigned cluster tables as a string, max. length n depends on the database system used

    The records of all cluster tables with the same key are stored under one key in the assigned table cluster. The values of the key fields are stored in the corresponding key fields of the table cluster. The values of all data fields of the assigned cluster tables are written as a string to the Vardata field of the table cluster. Besides the actual data values, the data string contains information on the structure of the data and which table it comes from. If the string exceeds the maximum length of the Vardata field, a continuation record is written with the same key values. The continuation records for a key are distinguished by their value in field Pageno. The actual length of the string in the Vardata field is stored in the Pagelg field by the database interface.

    You need the structural information stored in the ABAP Dictionary to read the data from a pooled table or cluster table correctly. These tables can therefore only be processed using Open SQL with the cluster interface, and not with Native SQL directly in the database.

    <b>In Repository informatino SE84 goto ABAP Dictonary -> Other Objects -> Pooled and clustered tables -> And then execute. It will give the list of available pooled/clustered tables.</b>

    For further reference check the SAP help document...

    http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ea0b446011d189700000e8322d00/frameset.htm

    Thanks and Regards,

    Bharat Kumar Reddy.V

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 12, 2006 at 05:09 AM

    HI

    GOOD

    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.

    EXAMPLES->

    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm

    THANKS

    MRUTYUN^

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 16, 2006 at 05:03 AM

    Hi Pavan,

    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.

    HOpe this helps u,

    Regds,

    Seema.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 16, 2006 at 10:14 AM

    HI Pavan,

    go through the following link.

    cluster-pool-and-transparent-tables

    Regards,

    Nagaraj

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.