High Processing Time for Transactions with Multiple System Interaction
Recently, I was asked to help one customer to check their SAP Retail bad performance problem (with no CPU and database bottleneck from EWA) which has large processing time in total response time of dialog work process for months.
Processing time per Dialog Step defination:
High processing time can be caused by a CPU bottleneck or a problem with communication between systems. (compared with CPU time)
As for this customer, their SAP Retail system interacts with SAP CRM and ECC system in real time by RFC. Take one transaction code MM42 change material as example, it takes around 30 seconds to save only one material change while the main time is consumed by RFC connection between SAP Retail and SAP CRM system.
(Single Statistical Records got from STAD with filter MM42)
We compared with one SAP retail system in customer landscape with no CRM interaction (with same hardware and data size), save material change took less than one second and no RFC shown in STAD single statistical records.
Then it is time to check for the RFC connection and CRM system performance, and also it possible changes data sync in real time to async mode….
Hope this blog will help to fix this kind of performance problem.