Solution : https://service.sap.com/sap/support/notes/142419 (SAP Service marketplace login required)
Summary :
Despite setting load distribution quotas for RFCs as per Note 74141, excessive resources are being utilized. This discrepancy arises because the load management in SAP operates mainly for asynchronous RFCs configured with specific ABAP language elements, excluding synchronous and ungrouped asynchronous RFCs. Resolution requires refining resource profile configurations, especially post Support Package implementation, to accommodate dynamic application behaviors. Optimal use of dialog processes and management of potential resource conflicts, like sporadic overloads in transactional RFCs, are critical. Tools like RSARFCLD and TH_ARFC_REQUESTS offer means for dynamic adjustment and resource status checks.
Key words :
abap language element call function func destination dest, abap language element call function func starting, dia work processes minus minimum number, profile parameter rdisp/rfc_ accesses, abap language elements leading, dia work processes multiplied, work processes minimum number, profile parameter rdisp/rfc_check = 2, basis support package sapkb61025, basis support package sapkb46d26
Related Notes :
| 1260137 | Work process status "Stopped RFC" by SAPLARFC (tRFC/qRFC) |
| 687497 | Standard setting for ARFC options |
| 549981 | Determining system resources for parallel RFCs |
| 541311 | CC-INFO: Parallel processes FAQ |
| 527481 | tRFC or qRFC calls are not processed |
| 400330 | Outbound Scheduler/qOUT Scheduler |
| 212727 | CC-INFO: FAQs for parallel processes up to Release 4.6D |
| 74141 | Resource Management for tRFC and aRFC |