Solution : https://service.sap.com/sap/support/notes/877979 (SAP Service marketplace login required)
Summary :
In scenarios involving RFC communication errors between external programs and ABAP systems, effective debugging can be achieved through RFC trace enabling. To commence, activate trace propagation in the ABAP environment via transaction RZ11, adjusting parameters like gw/export_trace_level. Subsequently, clear existing trace files, activate the RFC trace, and replicate the error. Post-error, deactivate the tracing mechanism and store the resultant trace outputs for analysis. Additionally, multiple methods, such as environment variable adjustments and ini file configurations, are available for trace activation in external programs, ensuring comprehensive error diagnostics.
Key words :
gw/export_trace_level = 1 rdisp/accept_remote_trace_level = 1 gw/accept_remote_trace_level = 1, system --> list --> save --> local file, --> trace --> gateway --> display file, relevant abap application server, file named dev_rfc, display gateway trace, software development kit, librfc analysis reason, remote function call, current rfc library
Related Notes :
| 1671898 | Aktivieren von RFC-Trace Dateien innerhalb von IS-M/AMC |
| 532918 | RFC trace generation scenarios |
| 413708 | Current RFC library |
| 176277 | Generating RFC trace information |
| 47682 | Activating the CPIC trace |