I have some dubts about block of users, if i block the user all his jobs will be running or will be stoped until the user was unbloked ? And if there are interfaces that go to the R/3 by RFC's will be blocked too or could go away ?
Yes, the idea is to block all users, jobs and RFC conections to our R/3 because the functional people wants to make some changes and then the users con go to work.
Any jobs scheduled / run for locked users and expired users will fail. The general practise for RFC communication is to create users of type 'communication' or 'system' to do the tasks, as they don't expire and their password does not expire.
In trx SU01 ('Logon data' - User Type) you will see the type of user you want to block. If your user has the dialog mode and you lock this user then he wont be able to login (dialog) to the system anymore, but if he has jobs or processes running in the systems these wont be afected by the lock.
Thanks for the infromation, we found that we can use two programs BTCTRNS1 and BTCTRNS2 to lock the jobs or the other option is to go SM37 and change the released to scheduled jobs to stop them, but not tested yet.
I we need to stop the interfases that goes to the R/3 too, this are by RFC's. Do you know some for that ?.
Ok, I got your point, so you need to stop or block certain processes like jobs or program interface right?
If your interfaces work with RFC you could disable those RFC connections in trx SM59... Check in this trx what kind of RFC connections your interface is using (probably internal or tcp/ip connections) and change the settings to disable them temporarily. Afterwards you can change them back and do test to make them work again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.