Workflow Wizard for approval of Purchase req with three levels of approval (in a hierarchy)

[Bradshaw-Long, Kathleen]

Thank you very much Mark.  I found some entries in the archive that are
very similar to my situation.
 
Kathleen
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Mark Pyc
Sent: Wednesday, January 21, 2004 5:10 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Wizard for approval of Purchase req with three
levels of approval (in a hierarchy)
 
 
G'day Kathleen,
 
Have a look at the archives at http://www.wugarchive.com/ and review
this years posts. There was a discussion 2 weeks ago on this topic.
 
You shouldn't need a multi-layered Workflow since a new instance will be
started for each Release Code. You simply need to determine appropriate
agents based on the Release Code.
 
Have fun,
Mark
 
 
 
 
 
"Bradshaw-Long, Kathleen" <Kathleen.Bradshaw-Long at getronics.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
20/01/2004 18:11
Please respond to SAP Workflow Users' Group
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Workflow Wizard for approval of Purchase req
with three levels of approval
(in a hierarchy)
 
 
Dear Workflow users,
 
We are on release 4.6C and implementing workflow for purchase
requisitions. We have set up our release strategies which include three
levels of approval for a requisition.  The approvals are hierarchical;
that is, approver 2 can't approve until approver 1 has approved, and
approver 3 can't approve until approvers 1 and 2 have approved.  We are
using the task overall release of purchase requisition.  We have also
set up an organization structure and created positions for Approver 1,
Approver 2 and Approver 3.
 
We created a workflow by copying the standard workflow template
(WS2000077) for purchase requisitions and manually started it.  It works
great with 1 level of approval. Now we are ready to start building and
testing a workflow for a requisition that requires a second and third
level of approval. We've started experimenting with the workflow wizard,
but didn't get far because the business object for the overall release
requisition
(BUS2105) does not have the Interface: IFApprove. We think that we
should copy the business object BUS2105 and add the necessary Interface:
IFApprove.
 
Are we going in the right direction?  In other words, is the workflow
wizard (SWF3) a better way to start or should we be trying to build the
hierarchy manually by adding subflows to our main workflow?
 
 
        Kathleen Bradshaw-Long
        BP/IS
 
> North America Operations
> 836 North Street
> Tewksbury, MA 01876
> Tel: 978-858-8909
>
        Kathleen.Bradshaw-Long at getronics.com
> <www.getronics.com>
>
>