Web Service Logging and Tracing 
The Web Service Support Utilities allow you to observe the processes in the Web service runtime. The utilities are as follows:
Web service logging.
Web service tracing, such as performance tracing, functional tracing, and payload tracing.
The Web service logging utility provides all necessary information about the location and context, and also a recommended action for errors in the Web service runtime. Based on this information a Web service user or system administrator can try to solve a problem, or contact the affected development department.
The Web service performance tracing utility provides information about the duration details of a Web service operation on the consumer and/or provider side. This information can be used by Web service runtime developers, Web service developers, and Web service users to identify performance problems.
The Web service functional tracing utility provides information about calling details of a Web service operation on the consumer and/or provider side. This utility should only be used by Web service runtime experts to identify problems from within the Web service runtime. Consider that one needs to know well the details of the Web service runtime to be able to analyze the functional tracing data.
The Web service payload tracing utility provides information about data sent and received via the HTTP channel, and also from and to the Web service consumer or the Web service provider. This tracing can be used by Web service runtime developers, Web service developers, and Web service users to check the data sent or received via HTTP, and also from or to Web service consumer or provider.
When one or more of these traces are activated on the consumer side, tracing information is sent to the provider side via the HTTP header. If the provider system is an ABAP back end with at least release 7.20 or 7.02, and this ABAP back end allows 'remote trace' (profile parameter: rstr/accept_remote_trace = true), the corresponding tracing is also activated on this ABAP back end.
Prerequisites
Your user must be assigned one of the SAP_BC_WEBSERIVCE_ADMIN_BIZ or SAP_BC_WEBSERVICE_ADMIN_TEC roles. For more information, see Authorizations.
Integration
Transaction SOAMANAGER also provides error and trace logs for the Web service runtime. The tools provided by this transaction are based on a different logging and tracing concept. They are configured, implemented, and viewed independently of the Web service support utilities described below. More information: Displaying Logs and Traces
The Web service support utilities can be integrated in transaction SOAMANAGER in future releases.
Procedure
Set the desired logging level and the period for which the information is kept in the log.
More information: Configuring Logging
Activate the tracing for a user, terminal, or request URI, and set the desired tracing level and options.
More information: Configuring Tracing
Use the information from the error log to solve Web service issues.
You can check the recommended action, or perform further analyses in the Message Monitor and the Sequence Monitor. More information: Displaying Error Log
Review the performance, functional, or payload trace records for Web service provider and consumer calls.
More information: Displaying Traces
Check the trace overview to find more information about a particular trace record.
More information: Trace Overview
Display all trace details to be able to perform detailed analysis of the runtime processing.
More information: Trace Details
Simulate a call to a Web service provider using the available payload data without starting a Web service consumer.
For more information, see Testing Web Service Providers with Playback.
Use the asynchronous message view to find information about messages that have not been delivered, or for messages for which there are no error log entries.
More information: Displaying Asynchronous Messages