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 Related problem

Former Member
0 Likes
506

Hi Friends,

We developed one code to do the functionality of VK12, our code is working fine for 700 records but if i try to process more than 700 record its going for dump,

if i give more than 700 record dynamically created an internal table is holding all records, but while i loop that internal table loop is running for first 700 records but after that code is going to dump, please help me to solve this problem.

here i have pasted a part of my code.

field symbol <fs_dyn_table> is pointing my dynamic internal table

Note: Initially i commited the changes after the endloop so i thought that commiting the changes for every 250 records may solve the problem, but that also got failed.

Dump message is: NO STORAGE SPACE IS AVAILABLE TO EXTEND AN INTERNAL TABLE

Thanks in Advance

Manikumar

Message was edited by:

Manikumar shanmugam

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
463

Hi Mani,

Try to restructure your logic.. you are doing a very large processing in a single loop and the processing has lot of tables..

Also, you have not refreshed the RV_KONDITION.. Fm tables..

Thanks and Best Regards,

Vikas Bittera.

3 REPLIES 3
Read only

Former Member
0 Likes
464

Hi Mani,

Try to restructure your logic.. you are doing a very large processing in a single loop and the processing has lot of tables..

Also, you have not refreshed the RV_KONDITION.. Fm tables..

Thanks and Best Regards,

Vikas Bittera.

Read only

Former Member
0 Likes
463

This is happening as there not enough ABAP memory to add more lines into one of the internal tables. Please go to the dump and read it carefully.

The name of the table which caused the dump will be mentioned. Now determine whether the Internal table is yours or in SAP standard. If the IT table is yours check how you can clear the Internal table.

It may due to a lot of records or due to faulty logic causing an infinite loop in the program in certain cases. Try refreshing that table after each record (totally depends on your functionality).

If it is SAP standard, you will have to determine how the IT is becoming so big (Maybe a case of infinite loop somewhere ).

Hope this helps. If not try posting the dump here.

Read only

former_member189059
Active Contributor
0 Likes
463

I think there is some setting in the system which limits the number of space available for internal tables

ask your basis person about it, because I had the same problem once and basis solved it by changing some settings in the system