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

tables

Can any one tell me difference between cluster, transparent and pool tables, where we can use these tables exactly

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

6 Answers

  • Posted on Oct 01, 2006 at 11:20 AM

    hi,

    The following are the table types used in SAP :

    <b>I. Transparent tables</b> (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.

    <b>II. Pool Tables</b> (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

    <b>III. Cluster Tables</b> (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.

    rgds

    anver

    if helped mark points

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 01, 2006 at 11:24 AM

    hi srikanth,

    More at this link.

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

    regrds,

    anver.

    if helped mark points

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 01, 2006 at 11:40 AM

    Hi namburi,

    1. The MAIN difference for usage purpose is,

    that we can read transparent table directly

    by using select statement,

    and we will get the proper data, as we require.

    2. BUT

    3.POOL and CLUSTER table,

    store data in some SPECIAL/ENCODED format,

    so for cluster we generally use

    some standard FM

    or use import/export.

    regards,

    amit m.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 01, 2006 at 01:04 PM

    Hi,

    The transparent table by defination exists in one to one relation between Data Dictionary and the Database. This is not the case with cluster and pooled tables.

    Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 01, 2006 at 01:40 PM

    Hi,

    transparent table: inner join is possible on

    this tables and contain user specific data.

    we can define secondary index

    cluster,pooled table: can't be joined and contains

    data related to system

    example:when customer related data is changed

    change information is sored in cdhdr,cdpos

    cluster table.

    cluster tables should be accessed using full key

    else performance will be poor.

    check below link

    http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21eb13446011d189700000e8322d00/frameset.htm

    http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ec17446011d189700000e8322d00/frameset.htm

    Regards

    amole

    Add a comment
    10|10000 characters needed characters exceeded

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

    Hi

    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.

    Hope this helps u,

    Regds,

    Seema.

    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.