Theoretical question - WF Design

[Susan R. Keohan]

Hi Richard, Raju,

Thanks for the feedback, but I am talking about conditions that occur within the workflow after a 
given approval step (who approved it, did they approve it or reject it, where should it go from 
here, based on who they are, etc.).  Much of the approval path should be determined by the N-step 
BAdi, but it's the deviations from the norm that I am concerned about.

We've had issues in the past with various conditions set/tested within the methods themselves, and I 
think I am leaning towards providing as much visibility to the process flow as possible,(via the 
workflow logs).  Although folks could also just learn how to drill into the container and see the 
various flags and indicators there as well.

However, Raju's comments are also valid.  We have several workflows that are 2 pages wide, by 3 
pages down.  That's why I am pinning all my hopes on the BAdi!

So many ways to skin a cat...

Happy WF-ing,
Sue

Richard Marut wrote:

> Sue,
> 
> Another option is to use a start condition. You could also code your own
> check function module and manually add it to the type linkages table. The
> start condition will not require an ABAP or Workflow resoucre, just someone
> who can understand conditions. The Check FM will require ABAP but will be
> easy to find.
> 
> Richard...
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Susan R. Keohan
> Sent: Wednesday, November 09, 2005 11:55 AM
> To: SAP Workflow Users' Group
> Subject: Theoretical question - WF Design
> 
> Hello all,
> 
> I am in the process of designing workflows for SRM 5.0 (Shopping Cart
> Release - using N-step BAdi, 
> PO, etc.).  My organization is very thin when it comes to workflow
> expertise.  Therefore, I ask the 
> following:
> 
> Is it better to put conditions, branching, etc in the workflow itself, which
> exposes the conditions, 
> but also complicates the flow, and would require a WF person to
> modify/maintain, or
> 
> put a lot of effort into the underlying ABAP, the theory being that it would
> be easier to find an 
> ABAPer who can maintain/modify the code.  The drawback, of course, is that
> the conditions are not so 
> visible.
> 
> There's no right or wrong answer... just food for thought.
> 
> Happy WF-ing,
> Sue

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu