Solution : https://service.sap.com/sap/support/notes/49730 (SAP Service marketplace login required)
Summary :
SAP Note addresses error messages during RFC communication due to improper handling of screens or lists and provides mitigation strategies. Errors occur when screens are sent without a corresponding GUI connection during RFC execution, resulting in termination messages such')
Keywords: CALL_FUNCTION_REMOTE_ERROR, DYNPRO_SEND_IN_BACKGROUND, SYSTEM_FAILURE, maximum sessions, asynchronous RFC, kernel patches. Solution strategies involve adjusting function module code to bypass screen outputs during RFC, ensuring RFC user is appropriately authorized, and using kernel patches for specific releases to prevent maximum session errors. For detailed optimal error handling, the kernel patch levels and error analysis instructions are indicated to ensure application stability and prevent RFC runtime errors.
Key words :
customer component bc-mid-rfc rfc priority recommendations / additional info category, attributes transaction codes sm21sm51st22su01 header data released, menu tools -> administration -> user maintenance -> user, cpic server sends screen &p1 &p2, full screen including menu bar, remote connection including logon data, external sessions 300208 single step debugging, software component version references, / __%pdfstyle%__font-size, __%pdfstyle%__ / } symptom
Related Notes :
| 1079446 | CALL_FUNCTION_OPEN_ERROR during RFC debugging |
| 710920 | CALL_FUNCTION_OPEN_ERROR for six external sessions |
| 673402 | |
| 507808 | RFC / Leave to Transaction |
| 300208 | Single step debugging of RFC calls |
| 174306 | Elimination of the roll area with RFC connections |
| 51349 | SAPGUI display in RFC via background or CPIC user |