De-activating workflows in runtime environment

[Becker, Stephan]

Abby, the quickest solution during go-live is the temporary opening of the
system for manual changes (scc4), make the settings in prod directly, close
the system again, and reverse the whole thing afterwards. You just need to
be careful and document what you're doing, so that you can reverse to
exactly the state you were in before. To record what you do while the system
is open, you can set in scc4 the automatic recording of changes on, then
you'll get a transport with the changes. This transport is really in this
case just a log, as you would never actually transport that stuff anywhere..
 
HTH,
Stephan
 
-----Mensaje original-----
De: Dywan, Abby [mailto:adywan at clarkstonconsulting.com]
Enviado el: 11 November 2003 01:36
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: De-activating workflows in runtime environment
 
Hi workflow experts -
 
Is there a transaction where a user can activate / de-activate a workflow
event linkage in a production environment?  My issue comes from the fact
that several of our workflows are based upon master data creation - and we
don't want the workflows to trigger for the conversion loads during cutover.
We can always send up transports to de-activate the workflows, perform the
load, and then send up another transport to re-activate the workflow - but
it seems like an awful lot of transporting.  And we can't just not setup the
workflow runtime system due to the fact that workflows will need to be
running for other modules at that time.
 
If anybody has any suggestions, I would really appreciate it.
 
Thanks so much!
Abby
 
Abby Dywan