Skip to Content

Viewing the Logs in SAP Sourcing On Premise

SAP Sourcing/CLM .log  and .trc file locations within the Netweaver file structure:


For example:


App_ server: 0

Node: 0



NW supports both log and trc files. The log files are therefore more or less equivalent to ‘normal’ log files, while trc files are more or less equivalent to ‘debug’ log files. However, NetWeaver Administrator supports independent configuration of log content.

  • Log into SAP Netweaver Administrator.
  • Navigate to Availability and Performance Management -> Log Viewer.
  • Here it is good practice to create a view.  If you have created a view already go to: show view -> custom view -> name of the view.  If you do not have a view: show view -> custom view -> Create New View.

  • Select Log Location -> Get all logs from -> Select value -> //JOO/server0 -> hit apply location


  • Select Filter -> application -> contains: -> hit apply filter

Ensure that there are no additional spaces in the contains field as this will break the filter.  Save the filter and set as default if you wish to view it easily later.

Debug Logging

Previously in Sourcing 5.1 debug logging was activated through the System Information Logs console and output the deug stream directly into  the default logs with the DEBUG tag appended to its entries which was not inkeeping with Standarad SAP Practice.

In SAP Sourcing 7.0 the logs can be set up to capture debug information from within the NetWeaver Administrator and be viewed from the log viewer.  Debug logs are store in the same directory as the standard logs but are of the file type *.trc as they hold  detailed traces of the application’s behaviour.

Debug logging can be activated in the following manner.

  • Navigate to Configuration Management –> Infrastructure –> Log Configuration

Debug trace conf steps v2.jpg

Step 1:

Select from the Dropdown Tracing locations.

Step 2:

Navigate through the folder structure to find E-Sourcing and set the severity to debug.

Step 3: 

Be sure to copy the trace severity changes to the subtree by using the ‘Copy to Subtree’ button.

Step 4:

Save the Configuration.

SQL Traces

NetWeaver 7.3 seems to align debug logging with turning on the SQL Trace feature which adds unnecessary information to the logs when troubleshooting/diagnosing issues.

SAP Help – Managing the SQL Trace covers how to update this configuration but I’ll place it here as well and have made bold the Switch Trace off component in Step 5.

Navigate to: Troubleshooting –> Database –> Open SQL Monitors –> SQL Trace –> Administration.


  1. Select a cluster node from the list in the Current SQL Trace Status per Cluster Node area.
      1. Cluster node details are displayed with SQL trace statuses, either On with a green LED icon, or Off with a grey LED icon.
  2. To activate the SQL trace for the cluster node, choose the Switch Trace On button in the Trace Administration area.The SQL Trace is activated for the selected cluster node.
  3. To evaluate the trace, choose the SQL Trace Evaluation function.More information: Evaluating SQL Traces
  4. To set additional options for the trace, you use the Trace Options screen area:
    • To add stack trace information to every written trace record, select the Add Stack Trace checkbox.
    • To add stack trace information to trace records that take longer than a certain time period in microseconds only, enter the appropriate value in the Threshold in Microseconds field.
    • To add stack trace information to trace records that contain matching method name calls only, enter the appropriate value in the Method Name Contains field.

  5. To deactivate the SQL trace for the cluster node, choose the Switch Trace Off button.
You must be Logged on to comment or reply to a post.