Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Memory for internal tables

Former Member
0 Likes
932

Is there any method to find out in "runtime" how much memory for internal tables is left ?

If there is, the programm could do a better reaction than runniung into a "dump"...

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
857

hi check this abstract from abap faqs:

<b>List of internal tables while debugging</b>

There can be times when you need a list of active internal tables while you are debugging ABAP code.

The first method, lets you see which table required a lot of memory

While on debug mode follow the menu path GOTO->Display condition->memory use

Select tabstrip: Memory use - ranked list

The second method provides a very detailed list

While in debug mode, choose GOTO->System Areas->internal information

A list appears on the debug screen

By default the area editbox contains a ?

Now enter DSEG in that field.

Press Return .

You will get a list of all the tables active in that program along with some other attributes.

The type and size of the records determine if they are internal tables and how many records there are.

You can play around and try the other area than DSEG, some are interesting.

link: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/840ad679-0601-0010-cd8e-998...

Message was edited by: Hemendra Singh Manral

Is there any method to find out in "runtime" how much memory for internal tables is left ?

If there is, the programm could do a better reaction than runniung into a "dump"...

5 REPLIES 5
Read only

Former Member
0 Likes
858

hi check this abstract from abap faqs:

<b>List of internal tables while debugging</b>

There can be times when you need a list of active internal tables while you are debugging ABAP code.

The first method, lets you see which table required a lot of memory

While on debug mode follow the menu path GOTO->Display condition->memory use

Select tabstrip: Memory use - ranked list

The second method provides a very detailed list

While in debug mode, choose GOTO->System Areas->internal information

A list appears on the debug screen

By default the area editbox contains a ?

Now enter DSEG in that field.

Press Return .

You will get a list of all the tables active in that program along with some other attributes.

The type and size of the records determine if they are internal tables and how many records there are.

You can play around and try the other area than DSEG, some are interesting.

link: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/840ad679-0601-0010-cd8e-998...

Message was edited by: Hemendra Singh Manral

Read only

0 Likes
857

Hi !

Thnaks for that but what I need is to find that out in a running programm by itself. I'd like to react in the programm by interacting to the user or something like that...

Regards

Rainer

Read only

0 Likes
857

have you tried TX: SE30 for abap runtime analysis

here you can check the performance of your internal table

at runtime.

Read only

Former Member
0 Likes
857

HI,

System Field: <u><b>SY-TOCCU</b></u>

After the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, SY-TLENG contains the amount of memory allocated to the relevant internal table.

Hope this solves your problem

Regards

Sudheer

Read only

0 Likes
857

Hi !

Thanks for that...

What unit are there values .. bytes, lines... ??

Regards

Rainer