2009 Jan 07 7:51 AM
Hi Folks,
I noticed that memory was held even after user came back to the selection-screen from the report output screen. Memory was released only after the user exited the transaction completely.
Is this standard? Can something be done to release memory after the user presses "Back" from the list display?
Thanks!
-Arthi
Hi Folks,
I noticed that memory was held even after user came back to the selection-screen from the report output screen. Memory was released only after the user exited the transaction completely.
Is this standard? Can something be done to release memory after the user presses "Back" from the list display?
Thanks!
-Arthi
2009 Jan 07 6:02 PM
2009 Jan 07 7:21 PM
Hello Arthi,
If report has any export/import, submit etc statement which deals with memory then make sure that they are cleared after use. Even variables, internal table etc after use free them instatnly.
Check following code on free memory-
http://help.sap.com/saphelp_webas620/helpdata/en/fc/eb3beb358411d1829f0000e829fbfe/content.htm
http://www.abapprogramming.net/2007/05/abap-memory.html
Following link gives more on memory managment-
http://help.sap.com/saphelp_nw04/helpdata/en/02/96253c538111d1891b0000e8322f96/frameset.htm
Thank You,
Nishikant Kumbhar.
2009 Jan 08 3:53 AM
Thanks guys, but what I'm looking for is not ways to reduce the memory consumed by the report/transaction.
I'm asking about why all the memory is still held by the transaction even after leaving the list display screen and coming back to the selection-screen.
I guess it could be because the sel-screen is part of the transaction and hence it doesn't release the memory.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |