Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How do we see the data in Cluster and pooled table?

Former Member
0 Kudos

Hi can any one tell me how to view data in cluster and pooled tables?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Arun,

Yes they can be very well viewed by Transaction SE16.

For a clarity in this issue look at the following:

Transparent tables (like BKPF, VBAK, VBAP, KNA1, COEP)

These table allow secondary indexes (goto SE11->Display Table->Indexes)

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

Pool Tables (match codes, look up tables)

Should be accessed via primary key or

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

No secondary indexes

Select * works fine bcoz all columns are retrieved

Cluster Tables (BSEG,BSEC)

Should only be accessed via primary key which enable a fast retrieval otherwise retreval will be very slow

There are no secondary indexes

Select * works fine bcoz all columns are retrieved

These tables have got efficient multiple rows operation when compared to single row operations.can retrieve specific columns (to cut down on the memory).

Aggregrate SQL functions (SUM, AVG, MIN, MAX, etc) are not supported and cannot be buffered

Buffered Tables (includes both Transparent & Pool Tables)

While buffering database tables in program memory (SELECT into internal table) is generally a good as far as performance is concerned ,not always necessary.

Some tables are already buffered in memory, mostly configuration tables.

If a table is already buffered, then a select statement would be fast.

To determine if a table is buffered: choose the 'technical settings' soft button from the data dictionary display of a table (SE12). All Pool tables should be buffered.

Thanks and Regards

Srikanth.P

Edited by: SRIKANTH P on May 27, 2009 4:30 PM

4 REPLIES 4

former_member555112
Active Contributor
0 Kudos

Hi,

SE16 does allow you to view the data of pooled and cluster tables.

Are you facing any difficulty?

Regards,

Ankur Parab

0 Kudos

You should also be able to use SE16N transaction for the same.

Regards,

S.Dakshna Nagaratnam.

Former Member
0 Kudos

Hi Arun,

Yes they can be very well viewed by Transaction SE16.

For a clarity in this issue look at the following:

Transparent tables (like BKPF, VBAK, VBAP, KNA1, COEP)

These table allow secondary indexes (goto SE11->Display Table->Indexes)

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

Pool Tables (match codes, look up tables)

Should be accessed via primary key or

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

No secondary indexes

Select * works fine bcoz all columns are retrieved

Cluster Tables (BSEG,BSEC)

Should only be accessed via primary key which enable a fast retrieval otherwise retreval will be very slow

There are no secondary indexes

Select * works fine bcoz all columns are retrieved

These tables have got efficient multiple rows operation when compared to single row operations.can retrieve specific columns (to cut down on the memory).

Aggregrate SQL functions (SUM, AVG, MIN, MAX, etc) are not supported and cannot be buffered

Buffered Tables (includes both Transparent & Pool Tables)

While buffering database tables in program memory (SELECT into internal table) is generally a good as far as performance is concerned ,not always necessary.

Some tables are already buffered in memory, mostly configuration tables.

If a table is already buffered, then a select statement would be fast.

To determine if a table is buffered: choose the 'technical settings' soft button from the data dictionary display of a table (SE12). All Pool tables should be buffered.

Thanks and Regards

Srikanth.P

Edited by: SRIKANTH P on May 27, 2009 4:30 PM

0 Kudos

Thanks for providing help.