If you want to record the internal SAP system activities, use the function SAP System Trace (transaction ST01).
The following components can be monitored using the SAP system trace:
· Authorization checks
· Kernel functions
· Kernel module
· Database accesses (SQL trace)
· Table buffers
· RFC calls
· Lock operations (client side)
The last 4 components can also be monitored using Performance Analysis (transaction ST05). For documentation on this, see Performance Trace Overview.
There are two ways of selecting what traces you want displayed. In the initial screen, select the components to be logged, and additional filters, if required. You can reuse the filters and restrictions from the traces that have these settings when the traces are evaluated.
The initial screen of the system trace looks like this:
Proceed as follows:
On the next screen, you can create a short text for a trace, and choose whether the new file that is created specifically for this trace should be automatically created, or whether you want to specify a file. If you do not specify an absolute path, a file of this name is created in the log directory. In the case of automatic file creation, the system determines the filename and stores the file in the log directory. The advantage of this is that, unlike a manually created file, the F4 help can be used for to search for the file from the analysis screen.
If you choose automatic creation, you can delete the file again in this transaction (use the button in the analysis screen). This is not possible if you specify a filename. If you want to delete this kind of file, you have to do so at the operating system level.
You can find further information in the following sections:
Enter transaction code ST01. Alternatively, choose Administration ® System administration ® Monitor ® Traces ® SAP System Trace.