Release strategy workflow

[Jose Burgman]

Hi there
 
Thanks for the help - its unfortunately my first encounter with =
workflow and
release strategies.....
 
Regards
 
Jos=C3=A9
-----Original Message-----
From: Shaelene Hooper [mailto:Shaelene.Hooper at intelligroup.co.nz]
Sent: 02 July 2002 03:18
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Release strategy workflow
 
 
Hi Jose
=20
The standard release strategy workflow operates on only 1 release step =
at a
time.  I think this may be where you are getting confused.
 =20
In transaction OMGQ, under the Workflow button, each release step is
assigned to an agent.  This agent may be an org unit, position or user =
ID.
When the purchase requisition is first created, SAP triggers the event
ReleaseStepCreated. The workflow then finds the agent for the first =
release
step that you have specified in your release strategy.  It does not try =
to
find all the agents for all the release steps in one go.  The workitem =
that
is sent to the agent is for only 1 release step.  When the workitem is
actioned, and the requisition is released, the requisition program then
triggers the ReleaseStepCreated event again.  This then triggers the
workflow, which then finds the agent for the next release step.  So you =
see,
it is an iteritive process.  The workflow is only working on one =
release
step at a time, so your user exit need only determine the agent or =
agents
for that particular release step.
=20
Regards
Shaelene Hooper
Intelligroup Australia
=20
 
        -----Original Message-----=20
        From: Jose Burgman [mailto:Jose.Burgman at palabora.co.za]=20
        Sent: Tue 07/02/2002 1:44 AM=20
        To: SAP-WUG at MITVMA.MIT.EDU=20
        Cc:=20
        Subject: Re: Release strategy workflow
=09
=09
 
        Hi there
=09
        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.
=09
        Regards
=09
        Jos=C3=A9
=09
        -----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
=09
=09
        Hi Jose,
=09
        It's OK for the inbox items to disappear from other user inboxes -
this is
        just the way that SAP works.
=09
        One workaround is to get the initial guy (the one who doesn't have
        authorisation) to replace the workitem.
=09
        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.
=09
        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.
=09
        Regards,
=09
        Tim
=09
        -----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
=09
=09
        Hi every -one
=09
        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
=09
        Regards
=09
        Jos=C3=A9
=09
        -----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
=09
=09
        Thanks for the collaboration:
=09
        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)=20
        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:
=09
        Workflow for requisition release "n=C2=BA 000000408091, step n=C2=BA
0000000003: is
        has not been possible to create work item (WL 410)
=09
        Work item 408092: It has not been possible to read the people in
charge
        of type A. (WL 840)
=09
        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
=09
        affecting. Thanks again.
=09