SAP Knowledge Base Article

2079993 - Collective note for performance issues in inventory management MM-IM

Version 4 Validity: 29.10.2014 - active Language English

Symptom
You encounter a performance related problem in inventory management transactions or reports and want to know what actions would be necessary
for performance improvement.

Environment
SAP R/3
SAP R/3 Enterprise 4.7
SAP ERP Core Component
SAP ERP
SAP enhancement package for SAP ERP
SAP enhancement package for SAP ERP, version for SAP HANA

Cause
In case the following notes would not help you resolve the issue you are facing and you need to open an incident at the SAP Support Portal please
note that there is necessary additional information required. Following this guideline you will be able to provide all the required details to SAP
Support for your issue in order it can be analyzed directly, thus helping to reduce the average processing time of the incident.

Resolution
1. General guidelines

I. If you have BADIs or modifications implemented in MM-IM, that could influence the system behavior regarding your issue, kindly try to verify
your problem scenario with deactivated BADIs.
II. During incident creation you will be given the option to search for notes about your issue. Please use this possibility since a large number of
issues can be solved by already existing notes. For some hints on efficient note search please visit this Wiki page: How to search the SAP
notes efficiently
Please also check the notes below to find potential solutions:

Performance in inventory reporting:

MB51/MB5B redesign
MM-IM-GF-PERF 1598760 * FAQ: MSEG extension & redesign of MB51/MB5B
MM-IM-GF-REP 1558298 * MB5B: Redesign of selection for performance optimization
MM-IM-GF-REP 1550000 * MB51: Redesign of selection for performance optimization
MM-IM-GF-PERF 1516684 * MKPF fields added to MSEG - Performance optimization
BC-DB-ORA 1567602 * DB dependent steps to support the redesign of MB51
MM-IM-GF-REP 1915056 * MB51: How to improve performance and resolve possible dumping / timeout issue

ERP accelerator
MM-IM-GF-REP 1902840 MB52: enable Accelerator on HANA in any case
MM-IM-GF-REP 1815190 ERP accelerator for transaction MB52 (2)
MM-IM-GF-REP 1795093 MB52: Increased runtime when using ERP accelerator
MM-IM-GF-REP 1751041 * ERP accelerator for transaction MB25
MM-IM-GF-REP 1711464 * ERP accelerator for the report RM07MMFI
MM-IM-GF-REP 1711463 * ERP accelerator for transaction MB5L
MM-IM-GF-REP 1710852 * ERP accelerator for transaction MB52
MM-IM-GF-REP 1710851 * ERP accelerator for transaction MB51
MM-IM-GF-REP 1710850 * ERP accelerator for transaction MB5B

SAP HANA as the primary database

MM-IM-GF-REP 1798101 * Performance optimization MB5B
MM-IM-GF-MISC 1827707 Performance improvement for buffered customizing tables

Performance in reservations
MM-IM-RS-RS 2058828 MB25: Performance problems after design change using EHP7 or SAP Note 1750809
MM-IM-RS 2029014 Performance optimization MB26 - pick list
MM-IM-RS-RS 1904393 MB25: Performance optimization during data analysis
MM-IM-RS-RS 1750809 MB25: Change of database selection
MM-IM-RS 1585321 * MB25: Decreasing the runtime

Performance in physical inventory

MM-IM-PI-REP 2056389 Performance problems after upgrade to EHP7
MM-IM-SOH 1882039 MI20+MI24 - Performance and display of unauthorized data
MM-IM-PI 1783676 Performance MB54 - Display of consignment stocks
MM-IM-PI 1782768 Optimization for MI20 MI24 Transactions
MM-IM-PI 1782096 Performance of MI22: Display PI documents for material
MM-IM-PI 1778874 Performance MIDO: Display of physical inventory overview
 Performance during goods movement
MM-IM-GF-LOCK 1985306 * Performance guide for goods movements

* Performance optimizations marked by the red asterisk require additional manual steps to be activated!

2. Performance trace

In order we can analyze the issue in most cases it will be necessary to trace the performance problem. Whenever possible please try to
reproduce the issue and trace it with transaction ST12, and attach the trace files to the customer incident. If transaction ST12 is not available,
trace the performance problem with transactions SE30 and ST05 parallel. Following SAP Notes and SAP Community Network Blogs will help
trace the performance problem on the correct way:

ST12 Trace :

It integrates the ABAP (SE30) and the Performance (ST05) Trace into one transaction. The ST12 transaction for customer systems is
delivered using the ST-A/PI add-on (standard add-on for service preparation). SAP Note 69455 provides further information on this
subject. The transaction is not translated. It is available in English only and has no official documentation. However, SAP Note
755977 includes a brief instruction.

On SAP Community Network page Single Transaction Analysis you can find more information about ST12 Trace usage.

SE30 /SAT (ABAP trace):

The ABAP Runtime Trace (SE30) - Quick and Easy

ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow

Next Generation ABAP Runtime Analysis (SAT)

ST05 (SQL trace):

The SQL Trace (ST05) - Quick and Easy

Please refer to SAP Notes 805934 and 31511, on how to analyze database performance.

For the investigation of performance related incidents attaching an SQL trace and an ABAP trace of the reported process is a
mandatory requirement.

Keywords
performance, mseg, mkpf, mb51, mb5b, redesign, mb02, accelerator, mb52, mb25, rm07mmfi, mb5l, mb51, mb26, mi20, mi24, mb54, mido,
goods movement, guide, laufzeit, fehler, laufzeitfehler, timeout

Header Data
Released On 29.10.2014 13:31:28
Release Status Released to Customer
Component MM-IM-GF-PERF Performance
Other Components MM-IM-GF-LOCK Material Block
MM-IM-GF-REP IM Reporting (no LIS)
MM-IM-PI Physical Inventory
MM-IM-RS Reservations
Priority Normal
Category How To

Product
Product Product Version
SAP ERP All versions
SAP ERP Central Component All versions
SAP R/3 All versions
SAP R/3 Enterprise All versions
SAP enhancement package for SAP ERP All versions
SAP enhancement package for SAP ERP, version for SAP HANA All versions