RM07DOCS dumped with TSV_TNEW_PAGE_ALLOC_FAILED

[#1]

Hi Experts,

I am executing transaction code MB51 or program RM07DOCS and it dumped.

I entered four plants only and left all other selection parameters blank. It took a long while to run and dumped.

The exact dump message is "TSV_TNEW_PAGE_ALLOC_FAILED".

Please see attached screenshot of my dump and let me know guys any comments or suggestions or advice you can give.

Note: My BA told me that he does not normally use the other filters/selection parameters. Just plant.

Thanks,

Newcloudguy

[Lakshmipathi · Accepted solution]

You need to convince your BA and educate him/her that MB51 is a powerful report, but it’s designed to work best when we help it narrow down the data. When we run it with only plant as a filter, it tries to pull millions of records, which is why it crashes or runs out of memory. By adding filters like Posting Date or Movement Type, we’re not limiting your access — we’re making sure you get the data faster, more reliably, and without system errors.

Still if you are not able to convince, then, you can create a screen variant for mb51 via shd0 with pre-filled values like plant, posting date. Assign it to a user or role. This lets your Business Analyst run MB51 with default filters, even if they don’t manually enter them.

The other option is to create ZMB51 which should be copy of RM07DOCS Program, where you can add standard variant via se38 or se80 where you can include default filters like Posting Date, Movement Type, etc. This gives full control and avoids dumps — especially useful if MB51 is used frequently with minimal filters.

But again, the current practice is strictly not recommended and if needed, you need to take it up to next level

[pawan__kumar]

@newguy_cloud Tell your BA: While just using plants might have worked in the past for smaller data volumes, our system now contains many years of data. To ensure the transaction runs successfully, we must provide a date range to limit the amount of data the program has to process in memory.

[newguy_cloud]

Hi MPavan, First and foremost, thanks for the quick reply. Aside from the dump I shared to you, he also tried to download his previous report, and it said, "no more storage space available". How could I convince my Business Analyst to add more selection criteria/parameters if he was used to encoding only plants? I feel he will insist even though it is not best practice. Please let me know how I could revert to him. Thanks.

[Lakshmipathi]

Adding to the suggestion already given, mb51 will pull all material documents for that particular plant which could be in millions and hence, the issue. To overcome from this issue, you should apply further filter criteria like Posting Date, Material Type, Movement Type etc. so that, you will get the desired result. On the other hand, if you must run this report with only plant as filter criteria, schedule a background job for that but definitely, even for background job, it is always best to have more filters

[newguy_cloud]

Hi Lakshmipathi, First and foremost, thanks for the quick reply. Aside from the dump I shared to you, he also tried to download his previous report, and it said, "no more storage space available". How could I convince my Business Analyst to add more selection criteria/parameters if he was used to encoding only plants? I feel he will insist even though it is not best practice. Please let me know how I could revert to him. Thanks.