cancel
Showing results for 
Search instead for 
Did you mean: 

T.Code MB51 report very slow processing

Former Member
0 Kudos

Dear Expert

We facing the problem in the t.code MB51. Its taking too much time to execute and display the results.

Please let me know if any one face the same issue and solve it or any SAP note regarding the same.

Thanks in advance

Partha

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Try to reduce the number of data fields to be processed by report RM07DOCS. 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.

Please have a look the following SAP note..

Note 357187 - MB51: Fields in field catalog / selection screen

Also consider 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

Please, try all these suggestions. I hope they can be of help.

Regards

Bhuban

Former Member
0 Kudos

Hello,

@bhuban thnx for the reply. Can you please guide me how to customizing view V_MMIM_REP_CUST" and to do the same in production system?

cheers

partha

Former Member
0 Kudos

Hi,

In dev system go to the t,code se16n-V_MMIM_REP_CUST-  execute ( F8)- here you can see the maintenance.....

After change and save one TR will be generate. transport it in qas . Test it QAS and if its work fine then move to in PRD.

Regards

Bhuban

Former Member
0 Kudos

thanks

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Partha,

Please see from the selection cirteria, if the same amount of selection is given compared to when the t-code was running fine.

Check in ST03 , where it is spending most of the time? - response times etc.

Then probably you can enable the trace from ST12 and run the t-code and see where it is blocking the time.

If the DB time is very high even with less selection, try to run update stats on DB and check it again.

If the processing time is very high, check with abaper.

Thanks,

Jagadish.

JPReyes
Active Contributor
0 Kudos

You need to do your basic troobleshooting first.... 

Did you run a trace to see if any particular statements are taking unusually long time?... did you check your system for performance bottlenecks?...

Regards, Juan