Since ITAB1 is a standard table (I am right?), there will be a slight quadratic effect. But this won't come out to 2-3 mins for the table sizes you mentioned. I would guess that the problem lies inside of your <build smartform> block. But an SE30 trace can tell you what't really going on.
Hi B M,
You can create the clasical report and convert spool to pdf instead of using smartforms. Smartforms function moudle calling in the loop it degraded the performation of the program.
For converting spool to pdf you can used the program RSTXPDF5.
Kind Regards
Ravi Lanjewar
Well, calling smartform processing for each item in each sales document definitely results in the long runtime.Who is supposed to read 278 pages? Maybe you can discuss the requirements with business and change the format of the PDF document to represent the sales orders in a different format?
Hi,
Loop inside Loop should be avoided. Instead use READ TABLE inside first loop.
Loop at itab1.
readtable itab2 where f1 = itab-f1 , f2 and f3.
endloop.
Hi BM,
This is the best practice.
LOOP AT itab1.
READ TABLE itab2 WITH KEY F1 = itab1-F1 F2 = itab1-F2 ........Fn = itab1-Fn.
Executable statements.
ENDLOOP.
Cheers,
Dineshwar Singh Eswar.
