Fwd: Re: Requisition Release with Four Levels?

[Susan R. Keohan]

Forwarded on behalf of Jim Sauceman (sauceman at UTK.EDU)...
>Suhas,
>
>Thanks for your response. I tried marking C2, C3, and C4 as workflow
>relevant and it kicked off separate workflows for each code as you said.
>However, my customer wants to see one continuous workflow log where she can
>view the entire history of who has approved the requisition and when. When I
>generate separate workflows, this complete history is fragmented into 3
>separate workflows and the system only displays the most recent. The release
>prerequisites and all works just fine, but I don't understand why I am
>limited to two release levels within a single workflow.
>
>I have thought about replacing the C2 and C3 release levels with User
>Decision tasks containing a Reject Button and a Release Button, going to a
>two-level release strategy, and issuing the final release as the last step
>in the workflow. Does anyone have any other suggestions?
>
>Our Purchasing Department made the decision that they did not want to see
>*any* line items from a requisition until *all* line items have been
>approved. They apparently had some bad experiences with attempting to fulfil
>partial orders and have decided against allowing "line item veto" as a
>result. In fact, I first wrote the workflow with line item approvals and was
>quite proud of it as my initial effort in SAP Workflow. However, they
>quickly opted for Overall Release after the first demonstration. Go
>figure...
>
>Thanks for the assistance!
>Jim
>
>----- Original Message -----
>From: "Suhas Sapre (Contractor)" <Suhas.Sapre at fcf.co.nz>
>To: <SAP-WUG at MITVMA.MIT.EDU>
>Sent: Wednesday, November 22, 2000 3:13 PM
>Subject: Re: Requisition Release with Four Levels?
>
>
>> Hi Jim,
>>
>> It looks to me that you need to mark C2,C3,C4 as workflow relevant.
>>
>> Separate Workflow is kicked off for every release code. When C2 releases,
>C3
>> will get workitem in his/her inbox and when C3 releases, C4 gets it and at
>> the end PR is is released.
>>
>> This works fine provided you  have put release pre-requisites and release
>> statuses properly to reflect the design of release stategy in
>customization.
>> Just to understand, what was the reason for using overall release strategy
>> as against itemwise release?
>>
>> Cheers,
>>
>> Suhas
>> > -----Original Message-----
>> > From: Jim Sauceman [SMTP:sauceman at utk.edu]
>> > Sent: Thursday, 23 November 2000 03:45
>> > To:   SAP-WUG at MITVMA.MIT.EDU
>> > Subject:      Requisition Release with Four Levels?
>> >
>> > Workflowers,
>> >
>> > We are on release 4.6B and using Overall Release for Purchase
>Requisitions
>> > and
>> > Business Object BUS2105 (Requisition). I am testing a Release Strategy
>> > that
>> > requires four release levels with all lower levels as prerequisites for
>> > the
>> > subsequent higher level. The first level code (C1) initiates the
>workflow
>> > and
>> > the second level approval (C2) can be done with no problem. However,
>when
>> > the
>> > third level release (C3) is executed, the Requisition is marked as
>having
>> > been
>> > released by this level, but the work item does not go away and the
>> > workflow
>> > does not move to the next step (i.e. level four (C4) approval). When I
>> > re-execute the work item, it says that the release has already been
>> > effected
>> > with release code C3.
>> >
>> > Incidently, only the second level release code is marked as "Workflow
>> > Relevant" because this is the point at which I want the workflow to
>assume
>> > control. I have tried marking levels two through four all as "Workflow
>> > Relevant", but this causes new workflows to be triggered by each release
>> > code.
>> > Our goal is to have a single, four-level release workflow with final
>> > release
>> > occuring at the C4 release code after C2 and C3 have been effected. Is
>> > this
>> > possible?
>> >
>> > Thanks for your help,
>> >
>> > Jim Sauceman.............................sauceman at tennessee.edu
>> > University of Tennessee..................Voice: (865) 974-2448
>> > Manager, Database and Technical Support..Fax:   (865) 974-4810
>> > Project IRIS Workflow Team Leader
>