Changing a workflow that ends after a single release/approval to accommodate more than one release/approval

[Bradshaw-Long, Kathleen]

Wouldn't we still get a second workflow? I think inserting a condition
step at the beginning would still allow the first workflow to complete?
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Flavio Oliveira
Sent: Thursday, July 22, 2004 1:27 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Changing a workflow that ends after a single
release/approval to accommodate more than one release/approval
 
 
Kathleen:
 
Why don't you create a condition step on the begging of your workflow
and if it is the first approval, pass through all the approval steps
and, if it is the second approval, go directly to the second approval.
 
Flavio.
 
 
>From: "Bradshaw-Long, Kathleen" <Kathleen.Bradshaw-Long at getronics.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Changing a workflow that ends after a single release/approval=20
>to accommodate more than one release/approval
>Date: Thu, 22 Jul 2004 11:20:35 -0400
>
>         Hello all,
>
>         I'm in need of some advice on how to adapt a workflow that=20
>currently ends after a single release to a workflow that can=20
>accommodate a second release.
>
>                 We have recently Gone live with workflow for purchase=20
>requisitions.  We are on SAP Release 4.6C.
>
>         Our worklfow includes only one release step and only  finance=20
>people are authorized to release purchase requisitions.
>             However, we have managers at the operations level who can=20
>review the requisition. Because our approval requirements changes so=20
>much, we
>         have made our tasks general so that the user can select the=20
>approver in an "ad hoc" manner, from an SAP user list.
>
>         Here's how we set up our workflow:
>             We used object type BUS2105 and the triggering event is=20
>that a release step is created.  The workflow initiator (who is the
creator
>of the req) first gets the      workflow and has to select the
>operations approver.  The operations approver reviews the req and then=20
>has some decision steps such as:
>
>         Return the requisition to the initiator (if the requisition is
 
>missing some information, for example)
>             Cancel the request (This completes the workflow.  An=20
>operations approver would do this if they did not want to send the
>requisition on to finance for   approval.)
>             Select the next approver
>
>          If the operations approver selects a finance approver, the=20
>finance approver reviews the req and then has the decision steps:
>
>          Return to initiator
>          Confirm ready for finance approval
>
>         If they confirm it is ready for finance approval, they are=20
>presented with the release requisition transaciton.  Now, they can
>either:
>          Approve/release the requisition
>              Reject the req
>
>         Everything has been working fine so far.  However,  we are now
 
>implementing workflow for fixed asset requisitions.  We want to be able
>to set up more than     one release for fixed asset reqs.
>         The first release will still be done by our finance
manager(s).
>         The second release will be done by our CFO.
>
>                I've set up the release strategy accordingly, but when=20
>we run the current workflow, it starts all over.  In other words, after
the
>first release/approval, the first       workflow is complete but a
>second workflow is generated.  This second workflow starts at the very
>beginning step by sending the initiator (purchase       requisition
>creator) a new worklfow asking them to select an approver.
>               We want to extend the initial workflow, not start=20
>another one. Ideally, we would like the finance person who performed
the initial
>release to either select the    next approver, or have the next
approval
>agent chosen automatically from the org chart.  How can we change our
>current workflow to     accommodate more        than one release level
>without starting a whole new workflow?  Any advice/tips would be=20
>appreciated.
>
>
>
>         Kathleen Bradshaw-Long
>         IPS
>
> > North America Operations
> > 836 North Street
> > Tewksbury, MA 01876
> > Tel: 978-858-8909
> >
>         Kathleen.Bradshaw-Long at getronics.com
> > <www.getronics.com>
> >
> >
 
_________________________________________________________________
MSN Messenger: instale gratis e converse com seus amigos.
http://messenger.msn.com.br