2009 Oct 29 5:51 AM
Dear all,
I am a BW guy. i have written ABAP program.
I have delivered the Program to Production .This program runs fine in all development and QA systems .But the program is throwing dump in the Production ( with an error SYSTEM_IMODE_TOO_LARGE).I got input as this is a memory issue and can be rectified by fine tuning the program
Could anyone help on this.
Please find the program in below link
[Program|http://www.4shared.com/file/144544927/3a37f230/REPORT_YSBWVASVAP_no_standard_page_heading.html]
Regards
Bala
Dear all,
I am a BW guy. i have written ABAP program.
I have delivered the Program to Production .This program runs fine in all development and QA systems .But the program is throwing dump in the Production ( with an error SYSTEM_IMODE_TOO_LARGE).I got input as this is a memory issue and can be rectified by fine tuning the program
Could anyone help on this.
Please find the program in below link
[Program|http://www.4shared.com/file/144544927/3a37f230/REPORT_YSBWVASVAP_no_standard_page_heading.html]
Regards
Bala
2009 Oct 29 7:43 AM
It is indeed a memory issue, but since I'm not able to look at your code right now I can only suggest you have a look at the memory your report is consuming. You can use the memory analyzer for that (there is a blog / article on SCN somewhere). In general I guess that some of your internal tables are 'too big' (too many entries), so initializing them could help (FREE). On the other hand, it is also possible to change the profile parameter abap/max_imode (basis administrator).
2009 Nov 02 7:34 AM
Please find the code belwo
Moderator message - Please respect the 2,500 character maximum when posting. Post only the relevant portions of code
Edited by: Rob Burbank on Nov 2, 2009 9:17 AM
2009 Nov 02 8:35 AM
Search Notes 409641, 417307, 419465, 548845 and 589997.
Regards,
Srinivas
2009 Nov 10 10:59 AM
The declartion of internal table was changed and used parellel cursor logic
and then program executed successfully