Show TOC

Function documentationTraces Locate this document in the navigation structure


With trace files, you can check the ICF runtime (in particular kernel functions) if troubleshooting with the debugger has not been successful.


You should only activate traces if troubleshooting with debugging has not been successful, and the analysis of the application process needs to be continued at kernel level.


Caution Caution

Note that the troubleshooting method described here can affect your system performance. You should therefore only activate it if you really need it. You are advised to monitor the corresponding settings regularly and to deactivate any functions you no longer require.

End of the caution.
  1. To activate ICF traces, call transaction SICF and select the service for which you want to activate them.

  2. In the menu, choose   Edit   Trace   Activate Trace  .

    Note Note

    The path for the service you have selected is displayed in the URL path in the ICF field.

    End of the note.
  3. Enter a validity period for the activation and define whether or not the trace is to be user-specific. If you select Only for Calls from SAPGui IP, the traces are only activated for calls from the active SAPGUI IP address.

  4. Specify the protocol (http or smtp) and the trace level (2 or 3) to be used.

    Note Note

    The entries in the trace files refer to the kernel functions and the way they run. These can normally only be interpreted by the responsible developers. If you need help analyzing trace files, contact SAP Support.

    End of the note.

    Note Note

    You can also use the Server Monitor to obtain information about the general state of the server. To do so, choose   Edit Menu   Server Monitor   Local Serve (or Entire System)  . You can use this information to find indications of potential performance problems.

    End of the note.