Solution : https://service.sap.com/sap/support/notes/878860 (SAP Service marketplace login required)
Summary :
To troubleshoot RFC communication errors between an ABAP system (client) and an external server program in SAP environments, the following steps should be executed: First, clear old trace files from both the external server and ABAP system. Then, activate RFC traces in the ABAP system via transaction SM59 and in the external server, ensuring appropriate settings are enabled based on Note 877979. Reproduce the error to gather detailed data, then deactivate the traces once completed. Save and archive the traces, documenting all relevant information for further analysis or for sharing with SAP support teams if external assistance is required.
Key words :
system --> list --> save --> local file, sap transport control program, maintain rfc bit options, call transaction sm59, environment variable rfc_trace_dir, front-end pc, file named dev_rfc, rfc bit options, solution required steps, files named rfcxxxxx_yyyyy
Related Notes :
| 944792 | Runtime analysis when you start external RFC servers |
| 777565 | Output of runtime information of tp (trace) |
| 532918 | RFC trace generation scenarios |
| 413708 | Current RFC library |
| 176277 | Generating RFC trace information |