Solution : https://service.sap.com/sap/support/notes/47682 (SAP Service marketplace login required)
Summary :
When encountering CPIC errors related to external program connections (error code RFC_IO5), the SAP note recommends enabling CPIC trace for detailed error analysis. Trace files, vital for identifying issues in communication between the gateway and the external program, are generated in specific directories based on the system setup and the origin of the program call. Configurations for tracing can be set in older releases using environment variables or the sideinfo file, while newer releases offer integrated R/3 system options for adjusting trace levels in CPIC and RFC connections. Essential directories for trace file retrieval include the instance work directory, the starting directory of the external program, or specific user directories depending on system configuration.
Key words :
gwmon nr=<sap instance number>menu -> trace -> increment/ decrement, choose menu optionsedit -> activate trace oredit -> deactivate trace, tools -> administration -> monitoring -> system monitoring -> gateway monitor, tools -> administration -> monitor -> system monitoring ->gateway moditor, relevant work process displays detailed information, usegoto -> trace -> gateway -> decrease levelto decrease, followinggoto -> trace -> gateway -> increase levelto increase, /usr/sap/<sid>/<instance>/work directory, menu options'goto -> existing connections', cpic_trace=environment variables---------------------setenv cpic_trace
Related Notes :
1391642 | TREX 7.00/7.10, BWA 7.00: Activating CPIC trace |
878962 | RFC tracing for ABAP-to-ABAP communication |
877979 | RFC tracing for external-to-ABAP communication |
516073 | Timeout during connection setup |
516027 | Gateway error due to terminated TCP connection |
376078 | CPIC, improved trace options |
308929 | Activating trace for SAP Logon Control |
84114 | Modeless F1 help is not started correctly |
65325 | Error files and trace files for Remote Function Call (RFC) |