Theoretical question - WF Design

[Dart, Jocelyn]

Hi Sue, 

With SRM BADI, my approach is:

1. Put a lot of effort in start conditions, e.g. exposing extra object
attributes, as they can be understood and maintained by non-workflow
personnel.  

2. Put a lot of effort in the BADIs as they can be maintained by
non-workflow personnel.

3. Minimise changes to the workflow - not just because this is workflow
specific but also because of the risk of upsetting the standard routines
that rely on the patterns in the workflow. 




Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 


-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
Of Susan R. Keohan
Sent: Thursday, 10 November 2005 4: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

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