2008 Jul 22 8:36 AM
Hi all,
The internal table (with the internal identifier "IT_424332") could not be
enlarged any further. To enable error handling, the internal table had
to be deleted before this error log was formatted. Consequently, if you
navigate back from this error log to the ABAP Debugger, the table will
be displayed there with 0 lines.
What does this mean?
What do I have to do to correct the problem?
Thanks.
deniz.
2008 Jul 22 8:38 AM
Your internal table is too big for your application server to handle. Check whether your internal table really does need to be so big. If so, then either talk to your basis people about making more paging available, or work out a way of making your program work without handling such large amounts of data at one time.
matt
Hi all,
The internal table (with the internal identifier "IT_424332") could not be
enlarged any further. To enable error handling, the internal table had
to be deleted before this error log was formatted. Consequently, if you
navigate back from this error log to the ABAP Debugger, the table will
be displayed there with 0 lines.
What does this mean?
What do I have to do to correct the problem?
Thanks.
deniz.
2008 Jul 22 8:38 AM
Your internal table is too big for your application server to handle. Check whether your internal table really does need to be so big. If so, then either talk to your basis people about making more paging available, or work out a way of making your program work without handling such large amounts of data at one time.
matt
2008 Jul 22 8:39 AM
Sounds like you ran a program that built up a huge internal table, larger than what your box could handle.
Better have a close look at that program, probably a customer one?
Thomas
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |