SAP Basis Tech Supports

Symptom
The RFC trace generation should support troubleshooting of RFC problems.
Other terms
RFC, trace
Reason and Prerequisites
SAP Support asks the customer to generate RFC traces.
Solution
Depending on whether the problem can be reproduced at any time or if it only occurs sporadically, you must use different methods for troubleshooting:
a) The problem occurs frequently or can be reproduced at any time:
Under these circumstances, you should transfer the trace files to SAP as described in note 532918.
b) The problem only occurs sporadically:
Prerequisite: The following steps only apply as of kernel release 46D or higher.
Remark:This note may only be used by arrangement with RFC development.
Make sure that the following dynamic profile parameters are set to the value “0″ on all application servers that are not relevant for trace generation while the problem analysis is being carried out:
gw/accept_remote_trace_level = 0 (as of Kernel 46D)
rdisp/accept_remote_trace_level = 0.
For more information about the profile parameters mentioned above, refer to note 573800.
For initiator system release <= 6.40, you can generate the traces as follows for sporadic cases (case b):
1) Delete the RFC-relevant trace files on the R/3 systems of the relevant communication partners:
SM59 –> RFC –> Delete traceSM50 –> Process –> Trace –> ResetSMGW –> Goto –> Trace –> Gateway –> Reset file
2) Increase the gateway trace level in the RFC initiator system:
SMGW –> Goto –> Trace –> Gateway –> Increase level
3) Activate the trace and limit the trace file size to a fixed size:
Set the following profile parameter in transaction RZ11: rdisp/TRACE_LOGGING = on, 10 m(10 m equals a size of 10 megabytes)
4) Prepare the search for a string pattern:
In transaction SM50, reset the trace level for all work processes to “0″ (enter “ALL” as work process type).
5) Define search patterns:
In transaction RZ11, set the following profile parameter: rdisp/TRACE_PATTERN_0 = PERFORM_NOT_FOUND(PERFORM_NOT_FOUND is used as search pattern.)If the profile parameter is not known or found in transaction RZ11, proceed as follows:
In transaction SE37, enter a “TH_CHANGE_PARAMETER” function module and set the import parameters as follows:
PARAMETER_NAME = rdisp/TRACE_PATTERN_0PARAMETER_VALUE = PERFORM_NOT_FOUNDCHECK_PARAMETER = 0
6) Increase the trace level for the work process type that issues the RFC call:
In transaction SM50, set the trace level for the relevant work process type (for example, “DIA”) for the following components to “2″:M (Task handler)A (ABAP proc.)Y (Scrn. proc.)
For example, enter “DIA” as work process type so that the trace is activated for all DIA work processes.
7) Execute the program until the search pattern is found for the first time in the trace file or in transactions SM21/ST22:
If the error text is displayed, the trace level for the relevant work process type is automatically decreased to “1″.
Decrease the gateway trace level:
SMGW –> Go to –> Trace –> Gateway –> Decrease level
9) Gather the trace files and send them to SAP:
Compress the trace files into the Work directory and transfer them to SAP as described in note 40024.
If the initiator system release > 6.40, generate the traces as follows:
1) Find out which RFC connection is used for the RFC calls to the target system.
2) Switch to SM59, open the RFC connection and activate the checkbox for “RFC-trace” under the “Special option” tab. (The trace is then automatically transferred to the target system independently of the profile parameter gw/export_trace_level).
3) Carry out all 9 steps described above.

Remark:
When you activate the user trace in transaction SM04, the profile parameter gw/export_trace_level is set internally to the value “1″ for the RFC connections involved, so that no changes are required to the profile parameter gw/export_trace_level or in transaction SM59.