Performance issue on KONV table

[Former Member]

Hi All,       i am facing performance issue with following select query. i have 5000 knumh values and i just want to check atleast one knumh exist in konv table or not. Can anyone help me to improve below select SELECT * FROM konv INTO TABLE lt_konv up to 1 row where knumh in lr_knumh. Note : No of entries(from Se11) in KONV table is very huge. getting runtime error after 90min. Regards, Praveen

[Former Member]

Why you are querying via KNUMH? KONV is cluster table. Only good way to select from it via KNUMV.

R

[Former Member]

Hi Praveen,

If your requirement is just to check if at least one entry exits then do the below piece.

Hope you are already removing duplicates from your range table

SORT LR_KNUMH BY LOW.

DELETE ADJACENT DUPLICATES FROM LR_KNUMH COMPARING LOW.

SELECT COUNT( * ) UP TO 1 ROW

FROM KONV

WHERE KNUMH IN  LR_KNUMH.

The above statement does not need any container to hold select data. If it finds even 1 entry, your sy-subrc eq 0.

Regards,

Raju

[Former Member]

Why you are querying via KNUMH? KONV is cluster table. Only good way to select from it via KNUMV.

R

[Former Member]

can you explain your requirement? may be we can suggest an alternate solution.

KONV is a cluster table and you should avoid reading from it without using all the primary keys.

[Ankit_Maskara]

Hello,

This advice won't help directly, but you should use Select....EndSelect when you want to fetch a single record and you do not have primary key in the where clause else go for Select Single.

BR.

[Former Member]

Hi,

ur statement should only last a few sec. you can try selecting via se16.your programm should take the same time.

for selecting single value, i would use "select single"-statement.

im not very common with the cluster tables. But maybe a new index can help?

regards

Stefan Seeburger.

[RaymondGiuseppi]

Cluster table behind KONV is KOCLU with only avalaible key KNUMV at databse level. So to fulfill your request system has to read the whole table to look for KNUMH in imported internal table...

Why are you performing this query on a counter field?

Regards,

Raymond