Activating Workflows

[jup(p)]

hi phil,
 
i think you need a transport to deactivate the triggering of the event :(.
to activate/deactivate the event triggering use the transaction swe2.
 
for the future you should use a check function for the event triggering
witch doesn't start the flows for the user who make's the mass update. so
you don't need a transport in the future if you
make a mass update.
 
Josef Herwig
 
 
 
----- Original Message -----
From: "Czerwiec, Phil" <Phil.Czerwiec at andrew.com>
To: <SAP-WUG at MITVMA.MIT.EDU>
Sent: Friday, November 01, 2002 11:10 PM
Subject: Activating Workflows
 
 
We have a number of workflows that sends notifications if certain fields are
changed on the material master.  These are working fine.  We occasionally
have a requirement to perform a mass update on the material master and need
to temporally de-activate these workflows.  Is there a way to de-activate
and activate these workflows without processing a transport or creating
repair in the production environment?
 
 
Phil Czerwiec
Andrew Corporation
----------------------------------------------------------------------------
--------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
----------------------------------------------------------------------------
--------------------