
In transaction SM21 System Loggingyou can use RFC to read logs created locally in all the instances of the SAP system. Instances that do not have an RFC connection can be accessed through the instance agent. The log of the local instance for a maximun of the last two hours is displayed by default. You now have the option to filter message attributes.
|
Basic Attributes |
Explanation |
|---|---|
|
Start Date/Time |
Time the log evaluation was started. Since the size of the system log file is limited, depending on system activity, older system messages may have already been overwritten. |
|
End Date/Time |
Time the log evaluation ended. |
|
Message Number |
Each system message is identified by a 3-character ID. The first two characters are the message group, the third is the sub-ID. |
|
Client |
Client in which the message was written. |
|
User |
User for whom the message was written. |
You can also choose to display high severity messages only.
|
Extended Attributes |
Explanation |
|---|---|
|
Extended Instance Name |
This field usually contains the local instance. You can also display system logs of other instances in the SAP system, or select multiple instances by entering patterns. An empty selection has the same effect as entering *- all visible instances of the SAP system are selected (with F4 help you can display all visible instances). |
|
Transaction Code |
Transaction in which the message was written. |
|
Work Process Type |
Type of the work process in which the message was written. |
|
Process Number |
Number of the work process in which the message was written. |
|
Program |
Message was written while this program was running. |
|
Package |
Each message is assigned to a development package by means of its message group (the first two characters of the message number). |
|
Transaction ID |
Transaction ID in Extended Passport (EPP). EPP IDs can be used to identify single actions and transactions system-wide. |
|
Overall Context ID |
Overall context ID of EPP. |
|
Connection ID |
EPP connection ID. |