topic Viewing - Internal Table Memory Used? in Application Development and Automation Discussions

Viewing - Internal Table Memory Used?

Former Member — Fri, 04 Dec 2009 05:55:21 GMT

Hello all,

I could understand the difference between Internal Table with occurs 0 and internal table with type declaration...

correct me if i am wrong, occurs 0 declaration occupies 8kb memory and header line 256 bytes...

But what i could not get is...

Where can i view this internal table runtime memory usage?? Should i have to check that in some transaction???

If that is the case, what transaction i should look at?? Can i view this in debugging mode??? I tried GOTO -> STATUS DISPLAY -> MEMORY USE and i have tried even SETTINGS -> MEMORY MONITORING ->MEMORY DISPLAY ON...Nothing worked..

I have searched a lot about this in SDN....But could not come to a conclusion......

Waiting for your replies....

Re: Viewing - Internal Table Memory Used?

former_member206377 — Fri, 04 Dec 2009 06:10:16 GMT

Hi ,

You can do that in debugger and also try tcode S_MEMORY_INSPECTOR.

Also, this might help you.

http://help.sap.com/saphelp_nw04/helpdata/en/75/358abcbcb911d5993a00508b6b8b11/content.htm

To find out how much memory internal tables occupy, In the debugger , choose Goto ->Display Condition ->Memory Usage. Choose Change Settings to display a window, in which you can choose the Internal Tables button.

Edited by: Vasuki S Patki on Dec 4, 2009 11:43 AM

Edited by: Vasuki S Patki on Dec 4, 2009 11:44 AM

Re: Viewing - Internal Table Memory Used?

nirajgadre — Fri, 04 Dec 2009 06:43:34 GMT

Hi,

to get the internal table used in the ru time you goto~~> classical debugger~~> goto~~->status display~~>memory consumption.

In tab memory use you will got all the table used by the program.

Re: Viewing - Internal Table Memory Used?

Former Member — Fri, 04 Dec 2009 06:48:59 GMT

Hello Vasuki,

I have tried what you said here [Goto ->Display Condition ->Memory Usage. Choose Change Settings to display a window]...But memory allocated seems to be same for Internal table with occur 0 and Internal table with type declaration...

I don't have authorisation here for DBG_MEMORY_DIFFTOOL or S_MEMORY_INSPECTOR unfortunately.....

Then how to conclude, occurs 0 declaration gives low performance when compared to type declared Internal Table??

Can you please suggest me some more???