Preventing users from updating data in a system

Question: We will be bringing down our Prod system for a number of days and want to give end users a system copy of Prod for them to use during that time. Knowing the users will ignore numerous messages that the system is a copy and not the real Prod system, we want toprevent them from doing updates to anything. Basically just inquire. Without removing all of the security roles with update from the users and locking all update transactions via SM01, is there a way to turn off update capability similar to configuration setting as "Not modifiable". Didn't think so, but wanted to ask anyway.

Answer:
We will be bringing down our Prod system for a number of days and want to give end users a system copy of Prod for them to use during that time. Knowing the users will ignore numerous messages that the system is a copy and not the real Prod system, we want toprevent them from doing updates to anything. Basically just inquire. Without removing all of the security roles with update from the users and locking all update transactions via SM01, is there a way to turn off update capability similar to configuration setting as "Not modifiable". Didn't think so, but wanted to ask anyway.
You could try to generically lock all lock objects.
Then, every user who uses a transaction in change mode should get an "Object locked by ..." message.
I think this is about the closest you can get without too much effort, but it's certainly not a 100% solution.

Answer:
Lock every object in the system? Every vendor master record? every customer master record? Every possible account?

You couldn't possibly do this. For instance if you locked a journal entry number the next journal entry would be available.

But there is another bizarre idea (that someone can shoot me down on). SM13 is a transaction that handles update management. Update management is something really good programmers do for transactions that update several tables across several screens. They update all the tables in an update task (i.e. function module) and perform a commit work. SM13 allows you to suspend all updating. Generally not a good idea because people still think they are working. Problem with this is that not everything is updated in update tasks.

Anyway have fun with this...
Copyright ?2007 - 2008 www.jt77.com