slow performance of alv report

[Former Member]

Hi,

I have developed Invoice Register Report in ALV,

there 25 Selection Feild all multiple range , 98 coulmns & 26 database tables r used . its a very bulky report.

i did optimized coding. still it is very slow . can anybody tell me the reason or any method to improve the performance .

Regards

Fozia

[Former Member]

Hi!

First try using SE30 to identify the slowest part of the program.

LOOP AT itab INTO wa WHERE ... this statement is VERY slow on internal tables with a massive amount of data.

Try optimizing the SELECT ... JOIN-s and the FOR ALL ENTRIES...

Pleace break-points to the slowest part of the program and count the program runtime after every modifications.

Regards

Tamá

[Former Member]

Hi Fozia,

As you are dealing with huge data it will be slow, however you can take some measures to optimize timing.

1. SQL trace ST05 -

---

> then chose the options accordingly.. trace on once you have executed the object

then trace off, list trace..... you can find out the difference.

Use Se30 in conjunction with ST05. do a runtime analysis for the same.

Also on top tips and tricks are mentioned which shows how can you improve the performance.

I am sure that you have taken care of small nuances like number of joins not more than three, use of for all entries as much as possible. Do remove dead code from your object though will not make any huge difference.

If possible to have an EWA Early watch analysis for your production then it would be best.

Mohinder

[Former Member]

Hi Mohinder,

thnx for the reply i have taken all the possible measures,

i have used for all entreis, didnt use into corresponding ,

didnt use select sinlge, use work area etc.

i have used se30 in which max time is taken by vbfa table and kna1 table.

can u plz tell me when we execute a report in se30 every times the analysis is different on chnaging the selection criteria. why it is so?

thnx n regards

Fozia

[former_member181995]

fozia,

just follow this below blog,

Amit.

[former_member200872]

Hi,

Check for DB Indexes on the fields you are accessing (SE11).

If you need one, go ahead and create it.

(remember - do it for non-key fields so that it is accessed by your queries).

Also, check if you are using key fields in the where conditions of your queries.

Regards,

Wajid Hussain P.