AW: WF task deactivated: PFWF cannot activate it

["Jäger Sascha,E2"]

Hey Amy,
 
i had a problem like that, too.
 
I used program 'RHMOVE30' for my transports.  Anyway=20
the task lost classification 'general task' and i had
to maintain the production, too.
In your case i would try to transport my workflows
with program 'RHMOVE30' and check every transported
object.
 
Regards
  Sascha
 
-----Urspr=FCngliche Nachricht-----
Von: Yu, Amy (amyy) [mailto:amyy at chevrontexaco.com]
Gesendet am: Donnerstag, 21. November 2002 03:43
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: WF task deactivated: PFWF cannot activate it
 
Hi,
 
I have a critical problem in production, here's my 2 questions:
 (Note we are using WorkFlow task not standard task)
 
1.  One of our WF task's classification 'general task' was changed, and
we got 'no infotype 1217' in production, we don't know who changed it,
we would like to know how to find out 'who did it' and how to prevent =
it
from happening?
 
2. Then after changing the classification back to 'general task', when
we tried to activate it using the transaction PFWF, it seemed to be
successful, however, when we check the status in SWETYPEENA or SWE2, it
still showed 'deactivate'.  Any clues?
 
I ran the SWU0 simulation, I got the following for my 'problem WF =
task':
Other receivers =20
   Tasks which do not use this event                   =20
          WF99900002   Release Purchase Order   =20
 
Whereas for other WF tasks that are currently active, they have the
following:=20
Potential tasks to be started                             =20
    Successfully started                                    =20
         WF99900044   POFIX:  Correct Verbal Order Errors          =20
 
When I ran SWI1, I noticed that there were WIs generated for my =
'problem
WF task' seconds before the transport of the 'correct classification' =
to
production, just wonder if the 'classification' caused some other thing
to go wrong?
 
SWU3 check OK too.=20
 
Amy