Hi Nagireddy,
If you are getting this runtime error due to internal table storage space (you will see "No more storage space available for exceeding internal table" in this case) then you can proceed with below options:
1. Try to avoid fetching unwanted fields if you there are any.
2. Each program will have some limitation to deal with data volume. Hence, optimize your code by checking if program is holding data in any other unwanted tables.
3. If you are modifying selected data at later part of program with COLLECT or other stetements, which can minimize the record count, then check if you can do samething at SELECT query level with aggregate functions like SUM.
4. Last but not least, this is where most of the storage issues will be resolved. Use cursors (OPEN, FETCH, CLOSE) with appropriate package size and get smaller chucks data into internal table and process it.
Package size can be determized based on the size of each record in your table.
If you are not confortable with fetching data into internal table due control break events or for some other reason then you can get into work area or field symbols.
Now, if you are getting this runtime error not because of storage issues then it could be cut-off time that your system has for fore-ground execution.
1. You need to use lightweight WHERE condition (with Indexes if possible). Share your WHERE condtion with SCN, if possible.
2. If everything is fine (field orders, selection of required fields etc.,) then you should check for alternate architecture to display this data (Back executions, Multiple screens, Additional Filters)
Regards,
Naveen