Workflow Review and Ad Hoc Anchor Step

[Mark Pyc]

The idea of a Review WF is that if an agent feels a particular process
is unusual and needs to be brought to the attention of some key users
or mgmt they can start a review WF (if it is set up). This review WF
then sends a WI to whichever agents are defined and allows them to see
the logs of the original flow. You would need to have a fairly complex
process and some very savy users to justify the development.

The ad-hoc anchor step is used heavily in EBP but is now also possible
in a normal backend system. The idea is that at certain points extra
steps can be included on the fly (at the request of a user). In EBP
this is for the addition of extra approval steps, for example an
approver may feel that the particular shopping basket contains a
specialist purchase and needs additional approval by a given expert
(I've seen it used in the case of large IT purchases). In reality you
can add in any extra logic at these points in a backend defined WF.

In both cases I feel the interface is so clunky/ugly that they're not
really usable in a backend R/3 system.

Have fun,
Mark


On 6/29/05, Maorriyan <maorriyan_santoso at yahoo.com> wrote:
> Hi all,
> I'm wondering actually what is the purpose of "Review
> Workflow" in reviewer tab on the workflow builder? And
> what's the purpose and how we used it in reality?
> 
> Actually I've same question the purpose (in reality)
> of ad hoc anchor step type?
> 
> 
> 
> Maorriyan
> 
> Send instant messages to your online friends http://uk.messenger.yahoo.com
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>