topic Re: table join in Application Development and Automation Discussions

table join

Former Member — Thu, 23 Nov 2006 08:31:35 GMT

Hello All

can join work on transperent table ,cluster table and pool table?

in my application i have 1 transperent table 1 cluster table and 1 pool table

Is join works on that ..if yes how to do this ?

thanks

Re: table join

Former Member — Thu, 23 Nov 2006 08:33:10 GMT

i think join not workin with cluster table and pool table

Re: table join

anversha_s — Thu, 23 Nov 2006 08:37:51 GMT

hi,

Transparent Table:

Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

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.

So join will not work for cluster and pool tables.

rgds

Anver

Re: table join

Former Member — Thu, 23 Nov 2006 09:12:51 GMT

Hi Mahya,

You can not use cluster & pooled tables in joins.

Re: table join

Former Member — Thu, 23 Nov 2006 09:22:43 GMT

good

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

Join works in all the kind of table.

thanks

mrutyun^