Wednesday, 16 November 2022

How to create trace for SAPFTP/SAPFTPA or SAPHTTP/SAPHTTPA RFC?

 


Create trace for SAPFTP/SAPFTPA or SAPHTTP/SAPHTTPA.

1.    Before enabling data tracing, go to transaction SE38, execute program RSFTP001 (for RFC destination SAPFTP/SAPFTPA) RSHTTP40 (for RFC destination SAPHTTP/SAPHTTPA) while setting the "Delete Trace" (either "x" or "X") to delete the trace.
This is important in order to clear up older tracing information which might pollute the newly generated trace file, making it more difficult for the Support Engineer to pinpoint the desired information in the trace log.

2.    Go to transaction SM59 and open RFC destination SAPFTP/SAPFTPA or SAPHTTP/SAPHTTPA.




3.    Check "Set RFC trace" in tab "Special options".




4.    Reproduce the issue.

5.    Run report RSFTP001 (for SAPFTP/SAPFTPA) or report RSHTTP40 (for SAPHTTP/SAPHTTPA).



6.    Check the report results and find the line "Current working directory (location of dev_ftp)". Different directories may be shown, dependending on whether it's a front-end or application server destination.

Examples:
RFC destinations SAPFTP/SAPHTTP, with "Start on Front-End WorkStation" activation type: C:\Users\*****\Documents\SAP\SAP GUI"
RFC destinations SAPFTPA/SAPHTTPA, with "Start on Application Server" activation type: E:\usr\sap\...\work (DIR_HOME) directory in transaction AL11

 7.    Open the directory referred to above in step 6 according to your RFC Destination and find dev_ftp, dev_rfc or RFC** files (for saphttp, please find dev_http).

 8.    Please send the mentioned trace files to SAP Support by attaching them to the case they're related to.

.9.    After sending the trace files to SAP Support, please turn off the flag "Set RFC trace" in transaction SM59.
This is important because leaving tracing enabled indefinitely will cause the trace log size to continue increasing, consuming storage space unnecessarily.


EmoticonEmoticon

Note: only a member of this blog may post a comment.