Performance Issue

[Former Member]

Dear All,

I am building a infoset - query report & one of the selection options on the selection screen is for RESB-EBELN. When i enter a Purch. Order no. & execute the query, it takes a very long time. This is because this field is not a primary field of this table & also there is no Index for this field.

I would like to know is there anyway i can improve the performance without creating an index on this field?

Await inputs.

Regards,

Vivek

[Former Member]

RESB is a very big table...Like 10 Million records on my system...

What I have done is an INNER JOIN with MARC, so I can limit the search by WERKS and LVORM...It's still slow, but at least is better...

Greetings,

Blag.

[Former Member]

Mr. Alvaro,

Thanks for the inputs, as you said the RESB table i am working on has about 18 million entries. An inner-join also would not really help much.

I just wanted to check with the guru's of ABAP to see if there is any way to get the same performace as I would get by creating an Index on this field. The reason i am looking for this is alternative is because i do not want to create more Indexes on this table.

As of now i have one alternative as suggested by you, i.e. using INNER JOINS, if there is any alternative would be glad to hear.

Vivek

[ThomasZloch]

Maybe you can use table EKET. This has EBELN in the primary key and RSNUM somewhere in the data.

Might be a way to quickly find reservations for a given purchase order number.

Cheers

Thomas

[Former Member]

Mr. Thomas,

I have just one thing to say to you ' THANK YOU VERY MUCH '. Your suggestion is just about perfect.

Regards,

Vivek