Solution : https://service.sap.com/sap/support/notes/1260137 (SAP Service marketplace login required)
Summary :
SAP Note discusses the issue of "stopped RFC" work processes in transaction SM50, involving scenarios where SAPLARFC time-outs and stops both UPD and BTC processes. Addressing circumstances of inadequate dialog (DIA) work processes due to mass data transfers or the tRFC/qRFC framework interruptions, it instructs on various meticulous fixes. Recommendations include updating RFC function modules' configuration, gateway resource optimization, and Dialog Work process management with specific parameter settings to prevent and resolve these blockages. Refer to linked SAP notes for detailed guidance on configuration settings and additional steps.
Key words :
abap statement set update task local, terms stopped rfc stopped cpic reason, processing/sending mass data, profile parameter rdisp/rfc_check, profile parameter rdisp/rfc_checkt, rfc function module allocates, gw/max_overflow_usage = 80 gw/req_stack_size = 150, executes remote function modules, trfc/qrfc solution solution, update function modules
Related Notes :
| 1403974 | Determining the maximum connections in transaction SMQS |
| 1250813 | SAPLARFC uses all dialog work processes |
| 934109 | Work process status "Stopped RFC" |
| 925855 | "Stopped CPIC" when you use tRFC or qRFC and local update |
| 726148 | SAPLARFC occupies all work processes, RFC cascade |
| 142419 | Resource distribution for RFC and tRFC/qRFC configuration |