Solution : https://service.sap.com/sap/support/notes/375566 (SAP Service marketplace login required)
Summary :
The overloaded entries in tables ARFCSSTATE, ARFCSDATA, ARFCRSTATE, TRFCQDATA, TRFCQIN, TRFCQOUT, and TRDCQSTATE degrade tRFC and qRFC performance in SAP environments. High interface load, "Error" statuses, and queues awaiting processing significantly contribute to this issue. Detailed analysis is recommended via transaction SE16, especially checking the ARFCRETURN field to determine whether entries relate to unprocessed or erroneous tRFCs/qRFCS. Solutions mentioned involve not deleting RFC entries hastily due to potential database inconsistencies and ensuring applications reliant on these tables maintain synchronized communication. Additionally, certain corrections and regular operation checks (e.g., in transactions SMQ1 and SMQ2) are advised to manage qRFCs effectively.
Key words :
transaction wedi -> control -> system process code, ale/edi rfc transmission problem, system constantly places queue entries, terms application link enabling, experience considerable performance problems, sap business information warehouse, ale/edi customizing, message -> process -> retry, system automatically postprocesses, customer relationship management
Related Notes :
| 706478 | Preventing Basis tables from increasing considerably |
| 435125 | Poor performance of tables used by CRM (Oracle only) |
| 407125 | Poor performance of Q and TRFC on ORACLE |
| 384077 | APO: Optimizing CIF Communication |
| 370601 | Composite SAP note: APO 3.0 and 3.1 performance |