cancel
Showing results for 
Search instead for 
Did you mean: 

How to extract data from table for huge volume

Former Member
0 Kudos

Hi,

I have around 200000 material doc number for which need to get material number from MSEG table but while using SE16 it gives dump , i have even tried breaking it into batches of 20000 records but still SAP gives dump on executing SE16 for MSEG. Please advise if there is any alternate way to get data from SE16 table for such a large volume.

Note: In our system SE16N does not work, only SE16 is there for our SAP version.

Thanks,

Vihaan

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

done

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Vihaan,

It is usually unprofitable to download the entire contents of a table. Better to select exactly the data you wish to see, using a transaction, a query, or a report.

Anyhow, if your SE16 dump is due to a timeout (exceeded the interactive time limit), you can run SE16 in background. SE16>enter table>enter selection parameters

Then Program>execute in background. In most systems, there is no time limit for background jobs.

Rgds,

DB49

Former Member
0 Kudos

Hi,

As you can see above it is ABAP run time error and not time out. Also I have Material number only as my output but still it is giving dump for more than 5000 .

Regards

Vihaan

JL23
Active Contributor
0 Kudos

for such volume you have to use a small ABAP report

Former Member
0 Kudos

Vihaan,

Normally you refer such errors to your basis team/DataBase analysts. There are DB and Basis settings that can eliminate this dump, but they typically need to be analyzed for adverse side effects.

Have you tried accessing the material docs using the standard transaction (MB51)?

Rgds,

DB49

Former Member
0 Kudos

Hi,

As I mentioned I already got material document numbers from MKPF table and now I wanted to have material number for all these material docs from MSEG but i am getting dump.

Thanks,

Vihaan

Former Member
0 Kudos

Hi Jurgen,

Thanks for the suggestion but in current situtaion i am not having any ABAP support so need to rely on non ABAP steps only and it seems the only option left is to execute it 50 times (I really doon't want to do that but no other option it seems)

Vihaan

Edited by: Vihaan on Mar 25, 2010 12:51 AM

Former Member
0 Kudos

Vihaan,

Yes, I understand, and the program is failing. Now we are talking about workarounds.

You could change your selection criteria from 5000 indivual mat doc numbers to a range of doc numbers,or a series of ranges of doc numbers. You could try wildcards. You will get more records than you need, but you can then externally filter the results once the program has successfully completed and you have the downloads.

Also, as another workaround method, have you tried MB51? If you could somehow coax the results you wish out of this transaction, you could avoid having to create a custom z program report.

Rgds,

DB49

JL23
Active Contributor
0 Kudos

do you get dumps while executing SE16 on table MSEG, or do you get the dump because you entered 20000 document numbers into the multiple selection ?

in case of multiple selections you probably have to go down to about 1000 as maximum.

What does the dump tell you about the reason? timeout?

Former Member
0 Kudos

Hi Jurgen,

Thanks for your reply.

I am getting Dump when i enter more than 5000 records as input parameter in MSEG, if I put more than that then it gives dump as "ABAP runtime errors SAPSQL_STMNT_TOO_LARGE ".

I understand that I can extract data restrciting 5000 every time but I have around 250000 material docs so that means if we consider batches of 5000 I need to run the step more 50 times--> 50 excel files. I wanted to avoid that as that is going to take lots of my time.

Any suggestion, please help.

Also wanted to highlight that apart from Material Doc number I am entering Plant (8 plants) and Mvt type (14 mvt type) also as input parameter.

Regards,

Vihaan

Edited by: Vihaan on Mar 25, 2010 12:30 AM