SAP Basis Tech Supports

Symptom
You think that an error has occurred in the Remote Function Call (RFC) communication between two ABAP systems. You require RFC traces to analyze this problem.
Other terms
Error trace, trace, error, analysis, RFC, Remote Function Call
Reason and Prerequisites
From an ABAP system (client) you call a function module of a different ABAP system (server) using RFC.
Solution
Required steps for trace generation:
1. Delete old trace files on both ABAP systems2. Activate the RFC trace3. Reproduce the error scenario4. Deactivate the RFC trace5. Save the trace files on both ABAP systems
Execute the individual steps
1. Delete old trace files on both ABAP systems
To delete the trace files, log on to both ABAP systems and call transaction SM59.
In the menu, choose: RFC –> Delete Trace2. Activate the RFC trace
Call transaction SM59 in the client system. Select the used RFC destination. Activate the trace flag on the “Special Options” tab page. In addition, maintain the RFC bit options or activate additional trace flags of other components. In this case, follow the instructions given by the support staff and the relevant notes.
In the server system, the profile parameter “gw/accept_remote_trace_level” (transaction RZ11) must be set to default value 1; otherwise, the RFC trace is activated only in the client system.
If RFC bit options and profile parameters are changed, take a note of the original values so that you can reset the relevant values after the reproduction of the error situation.
You cannot use transaction SM59 to activate the RFC trace for the destination NONE. To activate the RFC trace for the destination NONE, you must activate the user trace (transaction SM04) for the user that is used to execute the RFC. When you do this, you must set the profile parameter “gw/export_trace_level” (standard value =0) to 1.3. Reproduce the error scenario
Reproduce the error situation. To help analyze the traces, document the reproduction steps and write down the time when the error occurred and any error messages that were issued, for example.4. Deactivate the RFC trace
Call transaction SM59 in the client system. Select the used RFC destination. Deactivate the trace flag on the “Special Options” tab page. If required, reset the RFC bit options and the profile parameters to the previous values.5. Save the trace files on both ABAP systems
Call transaction SM59 in both ABAP systems. In the menu, choose:
RFC –> Display Trace
Then in the menu, choose:
System –> List –> Save –> Local File
In the new dialog box, select “unconverted”. A suitable file name would be “SM59_<SID>.trc”, where <SID> is the system ID (this may be extended to include the host name). The file is now stored on your front-end PC.
Pack the files into an archive file. You can attach the archive to the message (this is the best option for archives up to 4 MB). If the archive is larger than this size, ask the support to provide you with a sapmats container.