SAP system logs

The main system log, SAP systems can be seen by running transaction SM21

(Tools-> Administration->  Monitoring-> System Log). Displays a message with

the current SAP-instance. Log entries are read from the file specified by the

parameter rslg/local/file. By default /usr/sap/<sid>/<Instance_name>/log/SLOG <instance_number>. Parameter rslg/max_diskspace/local sets the size of the

log file. By default, 500000.

After filling the old entries are deleted. The size of the single record 192 bytes. 

You can collect log records from all application servers on the central instance. 

To do this, you must set a number of parameters. 

Details on the SAP Help Portal .

Transaction ST22 -view ABAP-system dumps. You can via the menu

"move to-> Reorganize" set term of storage dumps. The retention value of 

dumps depends on the frequency of analysis of your systems. Usually, 7 days is

enough. Dumps are stored in table SNAP.

You can enable Security Audit Log system. From this you can see log successful

and failed logons, user blocking users, run reports, edit the transaction key. 

Temporarily included in the transaction SM19. Constantly parameter 

rsau/enable = 1. Option rsau/local/file sets the directory where to store the

logs. By default,/usr/sap/<sid>/<Instance_name>/log/audit_ <instance_number>.

Via parameter rsau/max_diskspace/local audit file size is set for the day.

View history through the transaction SM20. Delete old logs transaction SM18.

There is also an option to activate auditing changes in tables. Write the profile parameter rec/client = XXX (client number).You can specify multiple

comma-separated mandates. For the required tables in SE11 in technical settings

include "change history". View audit transaction SCU3. The audit log is stored in 

table DBTABLOG.