‎2007 Nov 15 1:07 PM
hi experts
in one of my program the performance is getting affected in the abap statement not in the database access
the program logic goes in this way from the main program 3 performs were called for in the last performa onlythe entire processing starts
in that last perform it s callin for a report through submit and return statement , the called report s again refering to one include program.
in se30 the highest % it showssthe last perform that s said and the program that s called through submit statement the include program is not affecting the performance please tell mehow to change the report insucha wayi can improve the performance
please reply
will assign marks for sure
thanks in advance
‎2007 Nov 15 1:13 PM
Hi!
Use more selection parameters, during calling the other report.
Like this:
SUBMIT z_second_report
WITH s_matnr IN s_matnr
WITH s_werks IN s_matnr
WITH p_langu = sy-langu.
Etc...
Regards
Tamá
‎2007 Nov 15 1:57 PM
yes the report s called using some parameters only even then it s takin more time
‎2007 Nov 15 2:07 PM
Try running the called program (program called by the last perform) using the same parameters as passed to it by the last perform in transaction SE30 and analyse the performance of this program. In all probability the performance issue lies in this program.
‎2007 Nov 15 3:00 PM
the last perform statement is not directly calling the report after some processing only, then comes the submit statement so the parameters passed through the perform will not be ompatible with the report that is called for
‎2007 Nov 15 2:29 PM
Can you post the code of the perform that is causing the problem?
Rob
‎2007 Nov 15 2:54 PM
i cant post the code all our mails are being traced it s a very highly secured place if they trace my doc i will be put into trouble and also i dont have net in our office
‎2007 Nov 15 3:08 PM
From your as I understand your original message, your report is calling another report and it is taking a very long time in that step.
Obviously, the second program is taking time and that is the one to be analyzed. So, you put a break-point on the SUBMIT statement and see what are the parameters that being sent to the second program. Then, run the second program all by itself using the parameters you have noted down and analyze what the problem is.
If my response is totally off of your question, please clarify the question.
‎2007 Nov 15 3:07 PM
One area u can check is the report called using submit.
the problem will be in this report.
check if there are any selects with for all entries and the table is initial.
‎2007 Nov 15 3:10 PM
actually we take a very care of these concepts like we will never write the select statements without the validation so there s no chance for this
‎2007 Nov 15 3:07 PM
if the submit statement s replaced by call transaction will that solve the problem,
say like if i create a tcode for my program that s called through submit.
‎2007 Nov 15 3:13 PM
one thing u can do is call the report in update task, seperate from ur report, so that it will run independently.