Ansicht
Dokumentation

12431 - Tcode ME52 slow on V5R2 - should be MB52

12431 - Tcode ME52 slow on V5R2 - should be MB52

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Tcode ME52 slow on V5R2 - should be MB52

Good news, Victor!

But the bad news is: "Your" statement is only ONE of the
many - as Xmas is coming, let 's say: - "suboptimal" SQL statements
lurking around to bite us.

And as your story shows, everyone always puts the blame on the DBMS
first, instead of looking at the code...

Have a good time
Rudi

-----Ursprüngliche Nachricht-----
Von: Lin, Victor [mailto:VLinZPlastipak.com]
Gesendet: Freitag, 19. Dezember 2003 20:58
An: DoNotReply@consolut.eu
Cc: Wiesmayr Rudolf
Betreff: RE: Tcode ME52 slow on V5R2 - should be MB52


Hello Rudi,

It is a good catch that you found there is no MANDT=MANDT in the SQL statement.
The transaction is ok most of the cases, but very slow when executed with a
variant having about 500 materials. Without MANDT=MANDT, V5R2 considers the
large number of materials, which is the second field in the index, and generates
a "non-optimized" query plan.

Two indexes, MATNR-MANDT on MARA and MATNR-MANDT-WERKS on MARC, were created and
temporarily fixed the problem. (Pay attention to the sequence of the fields!) We
still want SAP to add the join condition so that everything can be back to
normal.

Sorry that the Tcode is MB52 instead of ME52.

Thank you very much,
Victor



Durban Tours - Südafrika Safari

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 1992 Date: 20240423 Time: 095707     sap01-206 ( 4 ms )