This blog post will guide you through the steps on how to check system activities before stopping SAP. This is an important step to ensure a smooth and successful shutdown of your SAP system
For certain activities, such as large posting jobs, you may find that some transactions have already been posted, while others have not. A subsequent restore may be problematic in such cases.
Follow these steps before a system shutdown:
► Coordinate the system shutdown with all departments affected. If a group of users has already scheduled an activity for the period during which you want to shut the system down, and the activity is dependent on a live SAP system, you may have to postpone your system stop and give a higher priority to the needs of these users.
► Create a system message (Transaction SM02) to inform all users of the planned system stop.
► Before you stop the system, make sure that no users are still logged on or active in the system (Transaction SM04 or AL08).
► In Transaction SM37, check whether any jobs are active or have been scheduled for the time during which the system stop is to take place. Reschedule all jobs or cancel the jobs that are due to either run or be started. during the planned system stop.
► Check whether any active processes are still running (Transaction SM50 or SM51).
► Use Transaction SMGW to search for any active RFC connections, which may indicate interfaces that are currently running. Use the checklist in Table as preparation for stopping the system.
| Task | Date | Initials |
| The following tasks must be completed in sufficient time before the SAP system is stopped: | ||
| Coordinate the system stop with all departments affected (e.g., accounting, shipping, distribution, etc.). | ||
| Create a system message to inform all users of the planned system stop (Transaction SM02). | ||
| Send an additional email notification to all users affected. | ||
| Reschedule jobs or cancel the jobs that are either due to run or be started during the planned system stop (Transaction SM37). | ||
| The following additional tasks must also be completed shortly before the SAP system is stopped: | ||
| Make sure that no active users are still logged on to the system (Transactions SM04 and AL08). | ||
| Make sure that no active background jobs are running (Transaction SM37). | ||
| Make sure that no active processes are running (Transactions SM50 and SM51). | ||
| Check for active external interfaces (Transaction SMGW). | ||
| How to stop the SAP system: | ||
| Stop the application server instances. | ||
| Stop the central instance. | ||
| Stop the database (optional). |