Skip to Content

SUM2.0 SP00 DMO in MAIN_NEWBAS/PARRUN_MKPF2_S4 running long during S4HAAN1709 conversion.

Jan 22 at 04:29 PM


avatar image
Former Member


We are in mid of S4HANA1709 conversion at phase MAIN_NEWBAS/PARRUN_MKPF2_S4, However is running since long. Even earlier phase last for long time and seems performance issue with these phases.


NEWBAS/PARCONV_UPG ran for almost 16 Hrs.

NEWBAS/PARRUN_MKPF1_S4 is running since last 7 hours.

For slowness, below notes are identified, Shall we apply it now as system is undergoing upgrade in MAIN_NEWBAS/PARRUN_MKPF2_S4 phase at 80%.

2525114 : Performance issue in material document conversion.

2500347: Performance of AUSP and IBINVALUES XPRAs.

2513245: Batch management can be defined in general or on plant le

2545998: High runtime for XPRA CK_XPRA_CONVERT_KALA_EXTRAC.

2553722: Performance optimiziaton of XPRA RMXPRAS4SIMIGRATION.

2496635: Dump DBSQL_SQL_DEADLOCK_DETECTED during XPRA phase.



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Shakeel Ahmed Jan 22 at 11:46 PM


DMO/SUM these tools show abnormal behaviour sometime and you can not find any answer on this site. You need to log an 'High Priority' incident with SAP OSS. They can only guide, many a time even product owners are clueless, we have faced this.

We faced a scenario where we had completed DMO (For S/4 HANA Migration) with 99.75% but rest 0.25% took 24 hours, it kept running. We were clueless about so was SAP (Product Owner).

All in all raise a ticket with SAP.



10 |10000 characters needed characters left characters exceeded