Solution : https://service.sap.com/sap/support/notes/532918 (SAP Service marketplace login required)
Summary :
To address the need for RFC tracing to troubleshoot communication issues, SAP provides guidelines detailed in multiple notes. Tracing methodologies vary based on the communication partner and server roles involved. Scenarios include external programs communicating with ABAP (Note 877979 for external RFC client, Note 878860 for ABAB as RFC client), ABAP to ABAP communication (Notes 878962 and 176277 depending on the user involvement), GUI communications (Note 1320424), and communications through SAP Java Connector (Note 628461). For SAP TP program specifics, refer to Note 777565. Implementing these guidelines will facilitate precise RFC trace generation in varied troubleshooting contexts.
Key words :
communication partner calls rfc, sap java connector, special user exists, sap tp program, external program abap, require rfc traces, generate rfc traces, rfc gui communication, external rfc program, tp program
Related Notes :
1421182 | Reasons for CALL_FUNCTION_SEND_ERROR |
1414429 | ABAP runtime error PARAMETER_CONVERSION_ERROR |
1320424 | RFC tracing in RFC-GUI communication |
1148023 | Data security for RFC trace files and RFC debugging |
878962 | RFC tracing for ABAP-to-ABAP communication |
878860 | RFC tracing for ABAP-to-external communication |
877979 | RFC tracing for external-to-ABAP communication |
827671 | RFCGUI_UNEXPECTED_DATA |
777565 | Output of runtime information of tp (trace) |
764480 | SAP WinGUI I18N Trouble Shooting |
760459 | RFC library fallback for the RFC_TRACE_DIR variable |
722514 | Reasons for SAP-RC=223 |
696275 | Activate the RFC trace in the SAP GUI |
633441 | Runtime analysis of RFC calls |
628962 | How to switch on the SAP JCo trace |
564612 | FAQ, Q+A, SM59, RFC destination, RFC error |
558254 | RFC trace generation for sporadic errors |
550878 | Easy DMS interface: Prerequisites |
545177 | FAQ: Preliminary steps in analyzing RFC connections |
441352 | OPEN-FI event 00501015 is executed unintentionally |
411777 | Saplogon: supply trace file |
176277 | Generating RFC trace information |
65325 | Error files and trace files for Remote Function Call (RFC) |
40024 | Transferring customer files to sapserv# using ftp |