Release strategy workflow

[Jose Burgman]

Hi there
 
We are using the SAP standard workflow with the user exit. How would =
you get
the agents so that the standard workflow sends them after each approval
step? The SAP method is also getting the agents all at once. The user =
exit
is only run once, when the requisition is saved.
 
Regards
 
Jos=E9
 
-----Original Message-----
From: phillips, tim [mailto:tim.phillips at SER.com]
Sent: 28 June 2002 06:43
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Release strategy workflow
 
 
Hi Jose,
 
It's OK for the inbox items to disappear from other user inboxes - this =
is
just the way that SAP works.
 
One workaround is to get the initial guy (the one who doesn't have
authorisation) to replace the workitem.
 
Just selecting workitem --> replace from the inbox menu will do this.  =
Then
everyone else will be able to see it again.  Thus, the challenge is =
just to
make sure that users are aware  of this, and that they actually do it.
 
I suspect the larger problem lies with your agent determination =
procedure,
tho'.  The initial guy shouldn't really be receiving workitems he has =
no
authority to execute.
 
Regards,
 
Tim
 
-----Original Message-----
From: Jose Burgman [mailto:Jose.Burgman at palabora.co.za]
Sent: Thursday, June 27, 2002 5:27 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Release strategy workflow
 
 
Hi every -one
 
I'm on 4.6C Hot Package 31. We're using the user exit to determine the
agents. We are using a release strategy with pre-requisites and per =
line
item. We have encountered a rather strange phenomenon. The workflow =
goes to
the relevant user's correctly. However, if some-one goes into the =
workflow
out of turn so to speak and tries to release the requisition - the =
message
not authorised pops up (correct) and he has to go out. If the first =
person
wants to release it, the item is now reserved (can't release) and then, =
to
add insult to injury, the work item disappears out of the inbox of the
person whose level he tried to release. Ok, if that does not make sense =
-
requisition has release M4. No-one has yet released it. M4 goes in and =
tries
to release it says for eg that he is not authorised for M2. He goes =
out. M1
tries to release - item reserved. And work item disappears from M2s
inbox..... I'm sure that this is not correct - does any-one have any
experience with this and know a work around? The reserved item can be
rectified by the user himself, but the workflow "vanishing" from the =
inbox
is a bit scary.   =20
 
Regards
 
Jos=E9
 
-----Original Message-----
From: Carlos Parra [mailto:carlos.parra at developers.com.co]
Sent: 27 June 2002 04:55
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WorkFlow Error
 
 
Thanks for the collaboration:
 
I have a problem with the Workflow for Requisition release of Order=20
(Item by Item). When I do the test to the WorkFlow transaction (SWUS) =20
W.F. WS00000038 with the corresponding parametros like: Codigo of=20
release and Request of order with the position and when I execute it=20
and the result is the following one:=20
 
Workflow for requisition release "n=BA 000000408091, step n=BA =
0000000003: is
has not been possible to create work item (WL 410)=20
 
Work item 408092: It has not been possible to read the people in charge =
 
of type A. (WL 840)=20
 
The event is generated but at the moment for arriving at step 000003=20
corresponding to task TS00007986 it does not follow. Simule already=20
reviews the release strategies and work, not that but it can be=20
 
affecting. Thanks again.