Workflow going to person who is not a possible agent

[Dart, Jocelyn]

Hi Deidre,
Try using the PFAC simulate/test option for the relevant rule to check what is happening.
I seem to recall the rule for that task is function module based so you may also be able
To get a programmer to debug it for you.
Jocelyn Dart.
 
-----Original Message-----
From: Boulay, Serge
Sent: Wednesday,11 June 2003 4:24 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow going to person who is not a possible agent
 
 
Hi,
 
Normaly the assignement to a position, ..., a job are dated. Have you verify that?
 
Serge
 
-----Original Message-----
From: Deidre Logan [mailto:deidre_logan at goodyear.com]
Sent: Tuesday, June 10, 2003 1:56 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow going to person who is not a possible agent
 
 
hello there,
 
I am hoping you all can help me with my problem.
 
We use WS00000038 with task TS00007986 for our purchase requisition release
strategy.
 
In the config we  tie the workflow to a position.  The position has one
user assigned, A073892.  The user shows up as being the agent of the
workflow items.
 
The problem is the workflow is also going to the old user, A133820 who use
to be assigned to the position.  This user is no longer assigned to the
position.
 
I have verified the the new user, A073892 does not have a substitute or
Auto Forwarding turned on.
 
I have tried to Refresh the Organization Environment.
 
What else can I check or refresh to see why the old user A133820, is still
getting the workflow items for approval.
 
thank you in advance for your assistance on my problem.
 
Deidre Logan
Goodyear Tire and Rubber Co.
 
(Embedded image moved to file: pic01416.gif)