topic Splitting internal table(dynamic) in Application Development and Automation Discussions

Splitting internal table(dynamic)

Former Member — Mon, 06 Oct 2014 15:48:47 GMT

Hi experts,

My internal table loads records more than 50,000 records at run time depends on user inputs ,and that internal table is in loop,I want to split that internal table into 5 or 6 or more than into internal tables, and loop each internal table so that loop doesn't go time out error.(exactly , I don't have an idea of how many records in internal table).

thanks in advance.

vijay

Re: Splitting internal table(dynamic)

Former Member — Mon, 06 Oct 2014 16:09:46 GMT

Hi Vijay,

I'm not sure about your requirement. You want to split the internal tables to 5 or 6 (dynamic) to prevent time out error, right? My questions is, are you sure you wouldn't get time out error after you successfully split these internal table and doing loops?

Say you have 50.000 records, and then you split to 5 internal table (itab). So, each itab have 10.000 records. When you do loop in these itab, you will still loop 50.000 (5 x 10.000) times. So, I think it will not solve your time out error issue.

I think it's better to fine tune the code inside the loop, or do it background.

Regards,

Surya Wijaya

Re: Splitting internal table(dynamic)

rajkumarnarasimman — Mon, 06 Oct 2014 16:15:20 GMT

Hi Vijay,

I Don't think splitting the internal table is going to be right option. To find the internal table length, use describe statement as shown below.


"To find the Length of the Internal Table
 DESCRIBE TABLE IT_FINAL LINES L_LEN.

And based on length of internal table, we can split the internal table and store the same into sub internal table using INDEX keyword.

Regards

Rajkumar Narasimman

Re: Splitting internal table(dynamic)

Clemenss — Mon, 06 Oct 2014 16:24:49 GMT

Hi,

first of all: Never LOOP AT itab INTO headerline, always LOOP AT itab ASSIGNING <field-symbol>.

This will speed up the loop that you never get a time-out.

Second: Do not split the table, rather define the table as SORTED. LOOP ... WHERE will use the KEY. If your ABAP version is not out of date, you can define secondary indexes on the table for furher enhancement.

Syntax is a bit tricky - will need to read the documentation when trying first.

The number of lines.of internal table is given by bulit-in function lines( itab ). Only for upward compatibility reasons DESCRIBE TABLE still works.

Regards

Clemens

Re: Splitting internal table(dynamic)

jrg_wulf — Mon, 06 Oct 2014 17:32:38 GMT

@Clemens Li: When advising obviously not so experienced programmers to use field-symbols, please don't forget to point out the potencial risk. It is safe enough, if you're only reading but still, it is not in line with most programming guidelines.

Hi Vijay,

Splitting your table won't get you anywhere. If you want to follow Clemens advice, then first, you'll have to check with your client, if use of field-symbols are OK for the sake of a bit better performance. But i don't think this will really do you much good.

A loop on an internal table of 50K shouldn't cause a timeout. So you'll want to have a closer look on what ever it is, that you're doing IN the loop. Or if it's realy just the loop and the transferring of data to the WA, ask yourself if you really need all the data.

Watchout for nested loops. Take care of repeated statements, that could as well be placed outside the loop. Do not do anything unnecessary whithin the loop.

When everything is properly revised and you still have a timeout issue, think about running the program in background. Some programs simply can't run in dialog with every thinkable selection criteria.

Best regards - Jörg