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

[Griffiths, Mark]

If no new second event is raised (switch on your event trace in SWELS and view the trace in SWEL) then you are probably missing an entry in your release strategy release code configuration - each release code needs a 1 or a 9 in the workflow relevant column.  You also may need to adjust your release strategies to use release prerequisites (i.e. prerequisite of code 02 is 01)
 
Hope this helps,
 
Mark
 
SAP UK
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Bradshaw-Long, Kathleen
Sent: Mittwoch, 21. Januar 2004 14:08
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Wizard for approval of Purchase req with three levels of approval (in a hierarchy)
 
 
Thank you, Lorena.  It's not working that way for us yet.  After release
code 01 approves, then the workflow is terminated and no new event is
raised for release code 02.  We are going to check the event linkage to
see if that is the problem.
 
Kathleen
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Lorena
Sent: Wednesday, January 21, 2004 8:25 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)
 
 
Hi Kathleen,
 
You don't need to use IFApprove interface, because when a PR is
released, a new ReleaseStepCreated event is raised for that PR. This new
event is valid only for the next Approver Release Code, then the WI is
asigned to the next approver resposible via role resolution.
 
Regards,
Lorena Lspez
 
"Bradshaw-Long, Kathleen" <Kathleen.Bradshaw-Long at getronics.com> wrote:
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
>
>
>
 
 
---------------------------------
Do You Yahoo!?
Todo lo que quieres saber de Estados Unidos, Amirica Latina y el resto
del Mundo. Vismta Yahoo! Noticias.