Solution : https://service.sap.com/sap/support/notes/366869 (SAP Service marketplace login required)
Summary :
Persistent entries within the ARFCRSTATE table with status HOLD, EXECUTED, or WCONFIRM adversely affect performance during tRFC/qRFC processing in SAP systems. These are due to programming errors, communication gaps post-execution pre-confirmation, and ambiguous interface specifications between tRFC/qRFC and applications. Corrective updates in various Basis Support Packages address the programming issues. Furthermore, specialized programs like RSTRFCER and enhancements in RSARFCDL help manage EXECUTED and HOLD entries effectively. Integration of the function module TRFC_LUW_FINISH or application of the SET_EXEC parameter in RSARFCDL ensures structured handling post-LUW processing.
Key words :
6d basis support package level 01also refer, 6a basis support package level 21 4, 6b basis support package level 13 4, 6c basis support package level 05 4, 1h support package level 85 3, 1i support package level 57 4, 0b support package level 48 4, 5b support package level 26 4, trfc/qrfc client arrived, basis support package
Related Notes :
| 1448418 | HOLDEXE entries in ARFCRSTATE and SAP Business Connector |
| 539917 | SQL error 601 when accessing "ARFCRSTATE" table |
| 490296 | Request jumps from green to red for unknown reasons |
| 448966 | CRM 30: Tables ARFCRDATA and ARFCRSTATE are not cleared |
| 442478 | Installation of qRFC Version 6.20.043 |
| 416169 | IDoc: lots of entries in ARFCRSTATE through tRFC inbound |
| 378903 | Queue status in SMQ1, SMQ2 and table ARFCRSTATE |
| 371004 | Clear tRFC queue in event of incorrect work items |
| 319867 | Installation of qRFC version 4.6D.025 |
| 166096 | qRFC installation for 3.xx, 4.0x, 4.5x and 4.6x |