How many records can be displayed?

[Former Member]

Hi,

I would like to ask if someone knows how many records can be displayed from alv report with internal tables?

I made an alv report and when I run it in Development it is OK.In productive the records are about 1700000 and I cannot run it. Is there any limitations in report with internal tables?

Thank you in advance.

[former_member241258]

hi

maybe that is depend upon memory space of internal table in production system.

check with basis people for increase memory space of internal table and then try.

[Former Member]

Good morning Krishna Murthy,

Firstly,I would like to thank you for your answer.

I use the tables BKPF and FAGLFLEXA for creation of internal tables. Do you know if the memory space of internal table is general or for the specific report with specific internal tables?

When you say" increase memory space of internal table" ,do you mean general or for specific internal tables?

[former_member241258]

hi

generally basis people will assign some memory to sap program's execution.

based on that memory, internal table will get space to load data when executing the reports.

so that i feel maybe that type of error to be got by you.

check it carefully.

[Former Member]

Krishna Murthy, thanks again.

I am going to communicate with basis people and I will check the error when they run it again.

[Lakshmipathi]

Whenever you add any post to your original query, please do so under "Comment" and not under "Answer", as you were not answering to a query but only providing additional informations as required by the member. Meanwhile, I have converted your above post from Answer to Comment.

[Former Member]

Krishna Murthy, thanks again.

I am going to communicate with basis people and I will check the error when they run it again.

[matt]

I have down voted this answer for two reasons:

1. The immediate cause is lack of memory, but the solution is simply to not select so much data

2. No half-way sane basis team is going to increase memory allocation for a report that cannot even be used in an sensible manner.

When answering questions, please consider the wider implications. Otherwise you lead the OP down a false route, which is not helpful.

[Sandra_Rossi]

"cannot run" but what happens exactly? short dump in ST22? what does it say?

[BaerbelWinkler]

Christina - 1.7 Mio records in an ALV sounds like way too much data for anything considered a meaningful selection. Who is going to look at or work with them? So, instead of trying to get them to display, how about restricting your selection to something managable?

[Former Member]

Bärbel Winkler thank you for your answer. I have a request to display the amount of each G/L account (RACCT) per document number (DOCNR) and Ledger (RLDNR) for one year. Now, the new request is to add in report the Document Type (BLART -BKPF) in order to run by Document Type. I am new in ABAP sap (I worked 4 months in this object) and I do not know how to handle and made these reports.

[Former Member]

Bärbel Winkler thank you for your answer. I have a request to display the amount of each G/L account (RACCT) per document number (DOCNR) and Ledger (RLDNR) for one year. Now, the new request is to add in report the Document Type (BLART -BKPF) in order to run by Document Type. I am new in ABAP sap (I worked 4 months in this object) and I do not know how to handle and made these reports.

[BaerbelWinkler]

If I were in your shoes I'd push back on the request and really question the requirements. Just throwing more resources/memory at it to fulfill it doesn't make much sense. What does the user do with 1.7+ million records? Downloading them into e.g. Excel will more likely than not just hit another size limit.

Should the data really be needed, downloading it somewhere and in smaller packages may be the route to go. But it really depends on what it is needed for.

[bertrand_delvallee]

Hello,

Even in Excel 365 there is a limitation at 1,048,576 rows. You have to add one more step in your report to filter results. For example you can split screen with a filter part in the top of the page and an overview result on the bottom.

I guarantee you no human will use a report that big. Moreover I suppose it takes tens of minutes to display and even scrolls/filter.

Best regards

Bertrand

[matt]

You are merely stating a requirement. You are not answering Bärbel's question.

As a developer, if you get requirements that don't make sense, you have a responsibility to push back. It makes no sense to have a report with 1.7 million records displayed on it. There is no feasible use for that amount of data in a report.

You should add a check to your selection screen so that if certain criteria are not filtered on, an error (or warning) message is displayed.

[retired_member]

https://help.sap.com/http.svc/rc/abapdocu_752_index_htm/7.52/en-US/index.htm?file=abenmemory_consump...

[raymond_giuseppi]

Who asked this to you, ask for actual purpose, no human will read so many records, look more like an export than a report. You could consider building a file for FTP by package or, if available, fulfill the requiremenr in BW or BI...

Also there are limitation in your system to protect other users performance, so you go for a dump for lack of memory or time out (ask basis, but don't expect too much)

[Former Member]

I would like to thank you all of you that answered me. The purpose of requirement is to check the amount of each document number/GL account and ledger for a year. Finally,they run it per semester in quality system and next to production system.

[former_member284740]

Although i'm not familiair with your system (Hana DB?), maybe you could try to use a CDS view and access the data with IDA?

[matt]

With 1.7 Million records, no-one is going to be able to check that amount of data. The requirement still makes no sense. Is someone really going to sit at a screen and go through every one of those 1.7 million records and check the amounts are correct? Or print off 17'000 pages of report?

It just isn't feasible.

For that reason, I'm closing this question. I don't think anything useful can be added.

[matt]

A SAP system has a certain amount of memory available and allocated to a user's session. The limit on the size of an internal table is that amount of memory.