SAP System Sanity Checks Post Maintenance Activities



As a SAP BASIS admin, we often need to performance system maintenance activities like SAP Kernel Upgrade, System Parameter Change, Patch Updates or any specific activity which need SAP system restart. Generally every customer will have their monthly schedule for maintenance activities for SAP system landscape, like 3rd Saturday of every month etc. But after maintenance activity is over, we need to make sure that system health is normal and no issues are there. So to address this, let’s check out what activities need to perform as SAP System Sanity Checks Post Maintenance.

SAP System Sanity Checks

Below is the list of transactions which are generally executed as part of Sanity checks post SAP system maintenance.

  • SICK :- Transaction code SICK is to determine Initial Inconsistencies, if any, in the system.
  • SM51 :- Transaction SM51 is to check the availability and status of each application server in SAP system.
  • SM50 :- Transaction SM50 provide view of all available work processed in logged in Application server. Normal condition is few work process in running or active status, no long running Work Process and most of the other Work Process are in Waiting status.
  • SMLG :- Transaction SMLG is for Logon Groups. It shows available groups and distribution of application servers to each group. Make sure each app server is part of the available logon group. You can also check System Response. Go to transaction SMLG, and then Goto -> Load Distribution. There you will see a response time of the individual application servers.
  • ST22 :- Transaction ST22 is to list the ABAP runtime errors that have occurred in an ABAP system as well as the relevant short dumps. No dumps or very few dumps is sign go good system health.
  • SM21 :- Transaction SM21 is used to check and analyze system logs for any critical log entries. The SAP System logs all system errors, warnings, user locks due to failed log on attempts from known users and process messages in the system log. No critical errors in SM21 indicates good system status.
  • SM37 :- Transaction SM37 gives overview of batch jobs in SAP system. Check for failed jobs and take actions if needed. Also if there are jobs which are long running than their normal runtime, do status check for each job via Job -> Check status. It will correct job status if it already finished but was not updated. If still job is long running, then report it to respective functional teams.
  • SMQ1 :- Transaction SMQ1 is to monitor Outbound qRFCs. Report any failures or errors in SMQ1 to functional team.
  • SMQ2 :- Transaction SMQ2 is to monitor Inbound qRFCs. Report any failures or errors in SMQ2 to functional team.
  • SM58 :- Transaction SM58 is to monitor tRFCs. No failures indicate good system health.
  • SM13 :- Transaction SM13 is to check status of Updates in SAP system. Make sure Update is active.
  • AL11 :- Transaction AL11 is to check define directory accessibility. Make sure the required interface directories are available and accessible via each application server in SAP system.
  • SM12 :- Transaction SM12 gives us overview of locks in SAP system. Make sure there are no long running locks or too many locks in system.
  • SM66 :- Transaction SM66 is for Global Work Process overview. It shows all active work process from all application servers. This give good view of activities running in system.
  • SOST :- Transaction SOST is to monitor outbound emails. Make sure no errors are there.
  • ST02 :- Transaction ST02 is for memory overview. There should not be many buffer swaps in SAP system. Also hit ratio should be always above 90%. Also keep eye on usage of memory areas i.e. Heap Memory, Extended Memory etc.
  • ST06 :- Transaction ST06 is for overview of OS level KPIs like Memory and CPU.
  • ST04 :- Transaction ST04 is to check DB heath of SAP system.
  • STMS (Connection Check) :- Check STMS for each system connection. Go to System Overview, Check -> System Connection.
  • STMS (Transport Directory Check) :- Like System connection, you should also check for transport directory. Go to System Overview, Check -> Transport Directory.
  • STMS (Transport Tool Check) :- Like above two checks, make sure to check for transport tool as well. Please use the same option like Check -> Transport Tool. In case of any error, please take the corrective actions.
  • SMICM :- Transaction SMICM is for administration of ICM. You can check the logs as well as monitor the available ports. Please use the option to check the ports availability and make sure that all the ports are green. Also check the ICM log for errors. In case of any errors are there make sure to take a corrective action.
  • SM59 (Important RFCs) :- In any SAP system landscape, connectivity of SAP system by RFC plays a very important role as part of the integration. Hence please make sure that the important RFCs are working fine. You can do those checks via transaction SM59. In case of any issue, do take the corrective action so that integration is working fine between the two SAP system.
  • Important Integration Points :- Like RFC connection, integration points with SAP system and other Non-SAP systems are very much important. Hence please make sure that the important integration points are checked and validated so that business operations can work seamlessly.
  • DB12 :- Use DB12 to check the backup availability of SAP system.
  • URLs
    • FIORI Launchpad :- Check and validate.
    • WEBGUI :- Check and validate.
    • NWBC :- Check and validate.
    • Web-Dispatcher :- Check and validate.
    • Load Balancer :- Check and validate.

Also Read

How to extract List of TRs Created in SAP System for all Clients

Once above checks are done, you can get overall system health status and thus take actions further if needed, before end user report any issue.


Please note that every SAP system is unique as per its setup and integration with other systems. Thus you may need to add further checks based on your SAP System landscape setup.



You may also like...

Leave a Reply

Your email address will not be published.

error: Content is protected !!