table konv

[Former Member]

table konv is cluster

how i can see the tables that made the KONV

[Former Member]

Hi,

Try doing this ....

1). Goto se12 and display the table BSEG

2). Click on the Delivery & Maintenanace tab

3). Double click on the Pool/Cluster field

4). On the next screen do a where used list

You will find all the related tables.

Regards

[ashish_gupta11]

Pass the VBAK-KNUMV and VBAP-POSNR fields

to KONV-KNUMV and KONV-KPOSN fields and fetch the data from KONV table

Or Do one More

Make 2 Itab < Itab1 ,Itab2 >

Make INNER JOIN between the tables to itab1.

move field of konv to itab2 with move -->

MOVE-CORRESPONDING ITAB TO I_FINAL.

READ TABLE ITAB2 WITH KEY KNUMV = ITAB-KNUMV.

and finaly make final_itab and move itab1 and itab2 to final_itab ]

write : / final_itab(include all field)

thanks & regards ,

Ashish

[Former Member]

HI

Can u be more little in ur question

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.

Tables Documentation

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/25c1f5d1-0901-0010-d495-e96d02a0...

Reward all helpfull answers

Regards

Pavan

[Former Member]

Hi,

Table Cluster KOCLU is assigned to table KONV.

You can check the name in the attributes of cluster table.

Details of table cluster KOCLU:

Field name DTyp Length

MANDT CLNT 3

KNUMV CHAR 10

PAGENO INT2 5

TIMESTMP CHAR 14

PAGELG INT2 5

VARDATA RAW 3800

Sandeep