Theoretical question - WF Design

[Jim Sauceman]

Sue,

My two cent's worth is that since ABAPers are a more abundant resource
(relative to Workflow designers) as much work as possible should be done in
ABAP. In fact, I have made many of our workflows adaptable by modifying
Z-table entries to add/remove steps thereby reducing the need for either
Workflow or ABAP programming changes. We also use this feature to allow our
various campuses (Knoxville, Memphis, Chattanooga, Tullahoma and Martin) to
"customize" Workflows (within pre-approved parameters) to their particular
business requirements. 

If you would like to discuss the technique and see if it is anything that is
applicable to your application, let me know.

Best regards,
 
Jim Sauceman 
University of Tennessee

-----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 12:55 PM
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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug