WF task deactivated: PFWF cannot activate it

[Jose Burgman [AST]]

Did you run transaction SWU_OBUF to refresh the buffers?
 
Jose
 
-----Original Message-----
From: Yu, Amy (amyy) [mailto:amyy at chevrontexaco.com]
Sent: Thursday, November 21, 2002 4:43 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: 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
______________________________________________
 
"This information is intended only for the person or entity to which it is addressed and
may contain private, confidential, proprietary and/or privileged material and may be subject
to confidentiality agreements.
 
Any review, retransmission, dissemination, or any other use of or taking of any action in
reliance upon this information, by persons or entities other than the intended recipient,
is prohibited.
 
If you received this in error, please contact the sender and delete the material from all
storage media.
 
The company is neither liable for proper, complete transmission of the information contained
in this communication, any delay in its receipt or that the mail is virus-free"