Solution : https://service.sap.com/sap/support/notes/61861 (SAP Service marketplace login required)
Summary :
SAP has identified performance issues related to incorrect index usage in various transaction processing scenarios involving the notification list, equipment list, and order list, among others. The core of the problem lies in the system's failure to utilize the most selective and relevant indexes during database reads, which affects the runtime adversely. Solutions proposed include restructuring or deleting certain indexes, modifying views, and updating join conditions to optimize performance. It is crucial to perform SQL trace analysis before and after implementing changes to verify the effectiveness of the corrections.
Key words :
onr00 mandt = jest mandt <- deleteonr00 objnr = jest objnr <- deleteonr00 mandt = onrqm mandt <- deleteonr00 objnr = onrqm objnr <- deleteqmel mandt = onrqm mandt <- deleteqmel qmnum = onrqm qmnum <- deletejest mandt = qmel mandt <- insertjest objnr = qmel objnr <- insertqmel mandt = qmih mandtqmel qmnum = qmih qmnumiloa mandt = qmih mandtiloa iloan = qmih iloanview viqmelst, add field objnr, field objnr, move field mandt, fields mandt, table jest, transaction se12 -> table qmel -> indexes, reading table qmel, additional key words riqmel20, table qmel
Related Notes :
| 871558 | Status board performance (ISE events) |
| 870977 | Status board performance (explosion of technical Objects) |
| 365744 | Expensive SQL Statement on VIQMEL or VIAUFK |
| 95944 | Improvement of performance correction Note 68682 |