SAP Basis Tech Supports

Symptom
The trace generation should support the troubleshooting of SOAP runtime problems.
Other terms
SOAP runtime, trace, syslog
Reason and Prerequisites
SAP Support asks the customer to generate SOAP runtime traces.
To process the problem, refer to Note 1006665. Note 1009109 will help you to better restrict the problem or to solve it yourself if possible.
Only implement this note if the system logged a SOAP runtime error in transaction SM21 (syslog) and the analysis according to Note 1009109 resulted in an error.
Solution
Perform the following steps to generate traces:
1. Activate trace;SM50 –> Process –> Trace –> Reset –> All FilesSM50 –> Process –> Trace –> Active ComponentsSet the following component trace and save your setting:
Trace level = 3
WpType = DIASelect the following components:
Taskhandler
ABAP proc.
Scrn. proc.
Security
ICFSMICM –> Goto –> Trace File –> ResetSMICM –> Goto –> Trace Level –> SetSet the trace level to 3.2. Reproduce the errors:Start your business scenario and reproduce the error.3. Deactivate the trace:If the error occurs, perform the following steps and deactivate the trace level you set previously.Before you do this, select all dialog work processes in transaction SM50.SM50 –> Process –> Trace –> Active ComponentsSet the following component traces:
Trace level = 1
Wp-Type = DIA
Choose “Default Vales” and “Save”.SMICM –> Goto –> Trace Level –> SetReset the trace level to 1.4. Collect trace data:SM21 –> Keep in mind the dialog work process number that logged the SOAP runtime error.ST11 –> dev_w<n> (n is the work process number from the syslog)ST11 –> dev_rfc<n> (n is the work process number from the syslog)SMICM –> Goto –> Trace File –> Save Locally5. Send the trace files to SAP:Upload the trace files to the relevant problem message.