topic Re: Optimisation issue in Application Development and Automation Discussions

Optimisation issue

Former Member — Tue, 23 Dec 2008 23:09:56 GMT

Hello gurus,

I have a code which is exceeding 10000 microsec timelimit. So there is a code dump.

Can u suggst me a way to replace this code.

SELECT imptt~point

APPENDING CORRESPONDING FIELDS OF TABLE tb_data

FROM ( imptt INNER JOIN iflo ON iflo_{objnr = imptt}mpobj )

FOR ALL entries IN ra_tplnr

WHERE iflo~tplnr EQ ra_tplnr-low

AND imptt~indct EQ po_indct

AND iflo~swerk IN so_swerk.

Thanking in advance!!!

Re: Optimisation issue

amit_khare — Tue, 23 Dec 2008 23:14:18 GMT

check this document -

http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm

also, I hope u are checking for internal table initial before using FOR ALL ENTERIES on it.

Also, it is preferable to SPLIT your select statement into 2 to perform better since you are using JOIN, FORL ALL ENTERIES and APPENDING all together.

Or execute the code in background.

Edited by: Amit Khare on Dec 24, 2008 4:47 AM

Re: Optimisation issue

Former Member — Tue, 23 Dec 2008 23:23:05 GMT

Could you simply tell me how should i remove the inner join?

Re: Optimisation issue

Former Member — Tue, 23 Dec 2008 23:24:25 GMT

Thanks for advice But The client said she doesn't want to execute it in background( Tough lady!! )

Re: Optimisation issue

Former Member — Tue, 23 Dec 2008 23:58:54 GMT

you can create a new index for that table.

the new index must have

Mandt and then all the fields that u are using in the where condition.

before creating the index i recomend that run txn st05, activate the trace, then run your query, stop the trace and try to find out wich join or where is with more rows.

good luck

Javier

Re: Optimisation issue

Former Member — Wed, 24 Dec 2008 00:12:37 GMT

Thanks. I have run st05 and found that this is the query( which i posted ) where i have maximum duration spent while running. Thats why i am asking you people to tell me an alternet way of doing the same thing which the uery does.

Re: Optimisation issue

Former Member — Wed, 24 Dec 2008 16:25:27 GMT

Ok,

U have 2 options then.

1) split the query in two or 3, you need to create a WA, and filled with all the data u need, not from a single query.

2) create a new index with the fields of the where condition.

FOR ALL ENTRIES is very very slow try to not to use it.

wheck if the stadistics are up to date (basis) sometimes the indexes may not work because of that.