Release strategy workflow

[Cathy Shelnutt]

Jose -
 
If you are truly using release prerequisites as it is designed, here would =
 
be a typical scenario:
 
Assume Approvals required:  Approver A, Approver B and Approver C=20
(prerequisites in place)
 
Approver A gets the message - they effect approval
Next Approver B gets the message - they effect approval
Next Approver C gets the message - they effect approval
Order is now ready for output to supplier=20
 
It is SAP design to remove the work item from the Inbox of other users=20
once a User has "reserved" the work item. The first thing I would ask you=20
is why are you sending messages to the Inbox of all approvers at once when =
 
you have release Prerequisites?  It sounds like this is where your problem =
 
is originating (your User Exit sending the Work Item(s) to all approvers=20
simultaneously).  Check that out and see where it leads.
 
Hope this helps.
 
Regards,
Cathy
 
IBM Personal Computing Division
ISC Solution Delivery - Procurement Team
Internet e-mail: cshelnut at us.ibm.com
Phone: 919-254-7864     Tie Line: 444-7864
 
In everything you do, put God  first, and he will direct you and crown=20
your efforts with success.  Proverbs 3:6, TLB
 
Mailing address:
P O Box 12195
Bldg 632/J156-B-12
Research Triangle Park, NC 27709-2195
 
 
 
 
Jose Burgman <Jose.Burgman at palabora.co.za>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
06/27/2002 12:26 PM
Please respond to "SAP Workflow Users' Group"
 
=20
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:=20
        Subject:        Release strategy workflow
 
=20
 
 
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=20
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=20
tries
to release it says for eg that he is not authorised for M2. He goes out.=20
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.
 
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
(Item by Item). When I do the test to the WorkFlow transaction (SWUS)
W.F. WS00000038 with the corresponding parametros like: Codigo of
release and Request of order with the position and when I execute it
and the result is the following one:
 
Workflow for requisition release "n=BA 000000408091, step n=BA 0000000003:
is has not been possible to create work item (WL 410)
 
Work item 408092: It has not been possible to read the people in charge
of type A. (WL 840)
 
The event is generated but at the moment for arriving at step 000003
corresponding to task TS00007986 it does not follow. Simule already
reviews the release strategies and work, not that but it can be
 
affecting. Thanks again.