13.07.2015 Views

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 10: R/3 System AdministrationSpecific Transaction Monitoring OverviewA user logged on to more than one terminal may indicate that the ID is being used: Used by someone else Used/shared by several peopleHere are some reasons not to share user IDs: If a problem arises, you will not know who created the problem.This situation makes the problem difficult for you to fix and prevent from happeningagain. Prudent security practices do not allow for the sharing of user IDs. Your external auditors may also perform this test to test your security.Release 4.6 allows you to prevent concurrent sharing of user IDs by activating thedisable_mult_gui_login system profile. We recommend that you activate this parameter.Transaction SM04 may show a user as active, when the user has actually logged off. Becausethe user session was not properly closed, the system “thinks” that the user is still logged on.This condition can be caused by one of the following: A network failure, which cuts off the user. Users who turn off their computer without logging off from the R/3 System.1. In the Command field, enter transaction SM04 and choose Enter(or from the SAP standard menu, choose Tools → Administration → Monitor → System monitoring →SM04-User overview).2. Select the user ID (for example,GARYN) to view the session theuser has opened.3. Choose Sessions.3210–44Release 4.6A/B

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!