MDRO run is making system very slow or MDRO run is dumping.
Reproducing the Issue
1. If any MDRO run is scheduled to be executed at an interval of few minutes (many a times customer schedule it per minute) then system has major performance issues.
2. Sometimes MDRO run is dumps due to temporary issues.
It is not advisable to schedule MDRO run within an interval of few minutes. Ideally it should be scheduled at an interval of 3-4 hours. Scheduling MDRO for less than 3-4 hrs may result in picking up the same records again and again. This may lead to locking issue there by consuming lot of CPU making the system very slow.
Another issue is that sometimes MDRO run dumps due to some temporary issue. In such cases it is observed that the subsequent runs of the MDRO turn green. In such a case it is advised to first check the application log of the MDRO. If the MDRO run is green for the subsequent runs then the ticket can be closed. If the issue has occurred more than 3 time please forward it to the corresponding application component.
If the system is becoming slow because of MDRO run then please ask the customer to schedule the run at an interval of more than 4 hrs.
For MDRO dumping, first check the application log of the MDRO. If the MDRO run is green for the subsequent runs then the ticket can be closed. If the issue has occurred more than 3 time please forward it to the corresponding application component. Also before forwarding get the permission of the customer to execute the MDRO.
KBA , AP-SLO , Sales Order Processing , How To