Poor performance mb51

[Former Member]

Hi All,

I have a problem with the transaccion mb51. I make a query with this filter: plant and storage location. Normally finished about 3 seconds, but now it´s takes about 8 minutes to finished. My question is: why is taking so long to finish this process? I will apreciate your anwers.

Best regards.

Edited by: Alvaro Olmos on May 25, 2009 9:15 PM

Edited by: Alvaro Olmos on May 25, 2009 9:16 PM

[Former Member · Accepted solution]

Hi Alvaro,

We have recently experienced similar issues in 46C and implemented OSS Note [921164|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=921164] to address this issue, perhaps you can refer this note to your ABAP team for review.

This OSS Note optimises runtime processes for MB51.

Hope this helps.

Thanks,

Ravelle

[Former Member]

Hi all

Just a little bit late, the problem was solve runninng a brtools statistics.

Edited by: Alvaro Olmos on Jul 21, 2010 10:49 PM

[JL23]

you do not specify a material?

so it reads all the material documents sequentially and filters according to your selection.

[Former Member]

Yes, that`s exactly Im doing. Im just have only a week of work on my servers that are working in production. I thing our records are to small to produce this kind of problem, but maybe Im wrong.

Edited by: Alvaro Olmos on May 26, 2009 6:03 PM

[JL23]

how many entries do you have in table MSEG ?

[Former Member]

I have exactly 37420 entries.

[JL23]

that is nothing, I have about 25 million.

Talk to you basis team, they can do a SQL trace to determine where it takes that much time.

Search OSS yourself or let the basis team search for MB51 and performance. There are a couple notes that can help.

[mauro_bianchi]

Hola Alvaro,

If the selection of MB51 is too general, the system has to select a huge amount of data from the database and there will come a point where the system limit is reached.

In the Report RM07DOCS behind transaction MB51 with the release 4.6 the access to the database tables with the MM documents MKPF and MSEG was optimized.The report itself cannot be optimized further regarding the database access time because it uses the most effective and straight forwards strategy. "Let the database to the job, it is the only instance

which has the knowledge". I would recommed you to check the correctness and freshness of the indexes for MKPF and MSEG.

In addition to that with report RM07DOCS it is possible to reduce the number of data fields to be processed. Each data field to be processed costs performance. The corresponding customizing view "V_MMIM_REP_CUST" allows to select and decrease the number of data fields from the MM documents.

In the standard system this customizing view comprises 56 data fields, which are marked for output. Please have a look at these fields and try to determine the fields you need in any case. Deactivate the output in view will "V_MMIM_REP_CUST" for all fields you do not need. This will improve the performance of MB51 because the volume of the selected data becomes smaller. The number of records is the same but the length of the records become shorter. The internal working tables become leaner, too.

I can recommend you the following :

- decrease the number of data fields in view V_MMIM_REP_CUST,

- restrict the selections of transaction MB51 for material, plant, posting dates, etc..

- start transaction MB51 in background mode,

- check the database statistics and settings,

- plan a reorganization of the MM documents.

Consider archiving some of the contents of the table which are no longer necessary. The relevant archiving objects are

MM_MATBEL and MM_SPSTOCK and can be archived via transaction SARA.

Hope this can help

Regards,

Mauro