<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=983340923-10112005>Hi Kjetil, </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=983340923-10112005>That's fine but this is SRM and often its a BADI we are
using to hold code rather than a BOR object. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=983340923-10112005>Particularly for the workflows Sue is talking about.
</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=983340923-10112005><FONT face=Arial color=#0000ff size=2>Plus
SRM has lots of special coding around the workflows so changing the workflow
patterns also requires a sensitive touch. </FONT></SPAN></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Kjetil
Kilhavn<BR><B>Sent:</B> Thursday, 10 November 2005 7:12 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Theoretical question - WF
Design<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005>One argument for putting more logic in the code is that
(in my opinion) it is easier to maintain BOR object code than re-arranging a
workflow. </SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005>However, the BOR object leaves no trail, so for
auditing adding workflow is better.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005>In the latest solution I designed I used quite a few
steps where the old solution hid stuff in the code. I like it because I can look
at it and see more clearly what goes on than with the old "massive-methods"
solution, and it will hopefully lead to fewer errors in the code as it becomes
less complex - my BOR code is unfortunately not perfect. Making the
workflow a little more complex also helps secure employment for at least
one workflow developer in the company ;-)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=486590208-10112005>So ... you have probably guessed it by now ... it
depends!</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil ØFT
KTJ ITS BKS SAP Basis</FONT></DIV>
<DIV align=left><FONT face=Arial size=2></FONT> </DIV><FONT face=Arial
size=2></FONT><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Raju
Omkaram<BR><B>Sent:</B> 9. november 2005 22:58<BR><B>To:</B> SAP Workflow
Users' Group<BR><B>Subject:</B> Re: Theoretical question - WF
Design<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>If WF log is critical then create a WF attribute long enogh to hold
the condtion. This attribute can be filled out in the BADI per each
condition that has been executed. In workflow create a step to display
the attribute. </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV>This way you can see what conditions have been set in BADI also it will
be easy to track the condition in question while keeping the WF simple
and elegant.</DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV>Raju </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial
color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff
size=2></FONT><BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 11/9/05, <B class=gmail_sendername>Mike
Pokraka (WUG)</B> <<A
href="mailto:wug.replies@workflowconnections.com">wug.replies@workflowconnections.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi
Sue,<BR><BR>Always a big question of keeping a balance between simplicity
and<BR>visibility. I lean towards visibility. Spend that little bit of extra
time <BR>in designing sensible subflows and you can cram quite a lot of
stuff into a<BR>flow that still remains manageable.<BR><BR>Another factor to
consider is putting as much 'business' conditions in the<BR>WF as possible
and hiding the techie stuff in code. Bear in mind that it may <BR>be
business users looking at the logs, so hiding too much makes
that<BR>useless. Oh, and it makes productive debugging easier to have stuff
in the<BR>flow.<BR><BR>Just my 2c,<BR>Cheers<BR>Mike<BR><BR>-----Original
Message----- <BR>From: <A
href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</A> [mailto:<A
href="mailto:sap-wug-bounces@MIT.EDU">sap-wug-bounces@MIT.EDU</A>] On Behalf
Of<BR>Susan R. Keohan<BR>Sent: 09 November 2005 19:55<BR>To: SAP Workflow
Users' Group<BR>Subject: Theoretical question - WF Design<BR><BR>Hello
all,<BR><BR>I am in the process of designing workflows for SRM 5.0 (Shopping
Cart<BR>Release - using N-step BAdi, PO, etc.). My organization
is very thin when <BR>it comes to workflow expertise. Therefore,
I ask the<BR>following:<BR><BR>Is it better to put conditions, branching,
etc in the workflow itself, which<BR>exposes the conditions, but also
complicates the flow, and would require a <BR>WF person to modify/maintain,
or<BR><BR>put a lot of effort into the underlying ABAP, the theory being
that it would<BR>be easier to find an ABAPer who can maintain/modify the
code. The drawback,<BR>of course, is that the conditions are not
so visible. <BR><BR>There's no right or wrong answer... just food for
thought.<BR><BR>Happy WF-ing,<BR>Sue<BR>--<BR>Susan R. Keohan<BR>SAP
Workflow Developer<BR>MIT Lincoln Laboratory<BR>244 Wood
Street<BR>LI-200<BR>Lexington, MA. 02420 <BR>781-981-3561<BR><A
href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</A><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE>
<P></P>
<P><FONT
size=1>-------------------------------------------------------------------<BR>The
information contained in this message may be CONFIDENTIAL and is<BR>intended for
the addressee only. Any unauthorised use, dissemination of the<BR>information or
copying of this message is prohibited. If you are not the<BR>addressee, please
notify the sender immediately by return e-mail and delete<BR>this
message.<BR>Thank you.</FONT> </P></BODY></HTML>