Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from horacio zapettini on Oct 3 at 8:06 AM Luca,
The short dump tells you the memory size limit you have. I'd take a different approach. Instead of having that big spool, I'd try to have a set of smaller spools and work with each one. I'd also avoid if possible the spool, but send the info to a custom table. It would be slower but I'd avoid some of the problems you're facing.
| | | ---------------Original Message---------------
From: Luca76
Sent: Friday, October 03, 2014 3:48 AM
Subject: Maximum Rows Of An Internal Table
The biggest problem is that I'm managing a spool, and in this case is a spool of about 50000 pages with 65 lines per page.
I'm using the function 'RSPO_RETURN_ABAP_SPOOLJOB' with parameters first_line and last_line,
setting a maximum of 50000 lines per calling.,
and using multiple internal tables to "split" the amount of records, to help me with other select
needed to extract other details that might even expand again the data (e.g. in the spool a found an invoice number and I need all the positions with BSEG), then I must write out everything on a file.
Hope you understand. :)
Thank you all!
Luca |
| Reply to this email to post your response. __.____._ |   _.____.__ |
