Solution : https://service.sap.com/sap/support/notes/176277 (SAP Service marketplace login required)
Summary :
The SAP Note details troubleshooting for RFC issues by describing methodologies to generate RFC traces, which are critical in analyzing RFC communication behavior. It outlines trace creation for user-specific scenarios and problems linked to specific RFC destinations or users. Advocating different techniques for R/3 application servers and external programs, the note highlights the importance of selecting the right approach corresponding to the system's configuration and the issue encountered. Trace files are generated and managed via transactions such as SM59, SM50, and SMGW, dependent on the type of application server or external program involved. Configurations and methods for activating and managing trace files across various scenarios are thoroughly explained.
Key words :
actual rfc trace files dev_rfc<work process number>, /3 work processes dev_w<work process number> document, work process-related trace files dev_w, menu option ->'process'->'trace'->'reset files', work process-related trace generation, creating specific rfc trace information, generating rfc traces vary, rfc-api functions rfcopen, actual rfc communication behavior, choosing edit->trace->'trace
Related Notes :
878962 | RFC tracing for ABAP-to-ABAP communication |
878860 | RFC tracing for ABAP-to-external communication |
877979 | RFC tracing for external-to-ABAP communication |
604564 | Initial help for SAP J2EE problems in WebAS 6.20 environment |
564612 | FAQ, Q+A, SM59, RFC destination, RFC error |
550878 | Easy DMS interface: Prerequisites |
532918 | RFC trace generation scenarios |
502562 | IPC: Activating RFC and JCO trace files |
483451 | SAPconnect: RFC trace on the external program |
371906 | Clarification of a WEB Reporting problem |
313971 | Monitoring: RFC error messages for SAPSYS users |
308929 | Activating trace for SAP Logon Control |
65325 | Error files and trace files for Remote Function Call (RFC) |