You can use the tracing function to analyze errors in logging and monitoring.
Trace information is technical – for example, header information - but it is also about business information (payloads).
The tracing information is available only in English. The tracing configuration is client-specific.
To configure tracing, your user must be assigned one of the following roles.
SAP_BC_WEBSERVICE_ADMIN_BIZ
SAP_BC_WEBSERVICE_ADMIN_TEC
These roles provide authorization for the authorization object S_WS_LGTRC with activity 36.
More information: Authorizations
Start SOA Manager (transaction code SOAMANAGER)
Go to the tab Logs and Traces.
Choose SOA Runtime Trace Configuration.
You can specify the following information, which the system uses to assign trace information at runtime to specific service calls:
Expiration time |
Specify the analysis period in seconds. The default is 300 seconds. |
User Name |
Specify the user to execute the Web service in the SOAP runtime. If you leave the field empty, the system creates a trace for all users. |
Interface |
The system will create a trace in the SOAP runtime for the calls of the interface that you specify here. |
Trace Level |
|
Accept Trace |
To copy the trace export, choose Accept Trace. |
Export Trace |
To export the trace from the SOAP header of the service consumer to the service provider, choose Export Trace. |
Trace Pattern |
The trace pattern is relevant if tracing is activated using the API. |
To reset tracing to the default value, choose Reset to Default Tracing.
To switch off tracing, choose Switch Tracing Off.
Even if there is an error, the system will not create a trace.
If you create an entry without specifying a user name and interface in the configuration table, tracing is activated for all users and interfaces during the SOAP runtime.
If you have made multiple entries in the table that overlap, the SOAP runtime will always apply the entry that leads to the greatest limitations.