6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 10: R/3 System AdministrationSpecific Transaction Monitoring OverviewThe following process should be followed before deleting a lock:TaskTransaction Code that Completes this TaskIs the user logged on any of the servers? Transaction SMO4 (without applicationservers) Transaction AL08 ( with application servers)If the user is not on the system, but transactionSM04 shows them on the system, delete theirsessions as described in chapter 9, Deleting a User’sSession. This step, alone, may clear the lock.Are there are processes running under the user ID? Transaction SM50 Transaction SM51Also see the Processes section later in this chapter.Are there batch jobs running under the user ID?Are there updates in process for that user ID?Once you know that there is no activity using the user’s ID:1. Select the lock entry for deletion.2. From the menu bar, choose Lock entries→ Delete. Transaction SM37Also see the Background Jobs section in this chapter. Transaction SM13Also see Failed Updates section in this chapter. Double-check the user ID of the entry that you selected to delete.If you delete the wrong lock, you could corrupt the database. Clear only one lock entry at a time. Do not use the mass delete option.This option will delete all the locks, not just the ones for the user you have selected.These transactions display all the users who are currently logged on to the system. Theyshow both the user’s ID and terminal name.In a smaller company, the administrator can recognize user IDs logged on to “unfamiliar”terminals. An unfamiliar terminal may indicate that someone—other than the designateduser—is using that user ID.System Administration Made Easy10–43