<!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.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>Mark & Larry,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>This is a very interesting conversation point which we have
debated in-house as well. There are certainly two aspects to a workflow
developer. The first skill set is that of the process analyst/
developer. Understanding the business process and the "big picture" is
essential to delivering a workflow that will benefit the business. Being
able to communicate with non-technical language to the business owners is
often neccessary. In those instances where this can be accompished with
SAP delivered workflow tools and BOT's, the cost to develop and support can be
minimal and does not require any ABAP skills. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>This second skill is that of the ABAP programmer/
developer. In the frequent circumstances where the standard delivered
workflow tools and BOT's are not sufficient to meet the business needs, a
talented programmer is needed.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>If you are fortunate to have all of those skills in one
individual, then in my humble opinion, you have the dream workflow
developer.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>(And by reading the emails in this group I can see that
there are several of these experts out there.) However, it is possible to
have those two skills reside in 2 different people, or even in 2 different
departments in a large global corporation. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>Best of luck to all of us in our various workflow
roles.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=546052014-09052006><FONT face=Arial
color=#0000ff size=2>Sherie</FONT></SPAN></DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT face=Tahoma size=2><B>From:</B>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Mark Pyc<BR><B>Sent:</B> Tuesday, May 09, 2006 10:09 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: WORKFLOW BEST
PRACTICES<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>I guess this gets into the world of demarcation disputes. If you have a
situation where the WF developer creates a method as a wrapper for a function
but asks a more qualified developer to deliver that function than the statement
could hold true. It really depends on how many people you have to change the
Workflow lightbulb. </DIV>
<DIV> </DIV>
<DIV>On the whole though I believe that the inherent logic of a Workflow and the
common need to pull apart the standard system (looking for event trigger points
mainly) requires a strong developer regardless of how much code they cut.
<BR><BR>Have fun,</DIV>
<DIV>Mark</DIV>
<DIV> </DIV>
<DIV><SPAN class=gmail_quote>On 5/9/06, <B class=gmail_sendername><A
href="mailto:lianghuan.x.hu@accenture.com">lianghuan.x.hu@accenture.com</A></B>
<<A href="mailto:lianghuan.x.hu@accenture.com">lianghuan.x.hu@accenture.com
</A>> wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV style="DIRECTION: ltr">
<DIV dir=ltr align=left><SPAN><FONT face=Arial>Sherie:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial>Thanks for sharing the
document. But I do not agree with one point under "Workflow and ABAP" on
Slide 9 which says that a workflow developer needs only " <U>light</U> ABAP
knowledge". In fact, a workflow developer is an ABAP developer with additional
workflow skills. A workflow developer has to write all kinds of ABAP code
that regular ABAP developer does, the only difference is that he has to put
his code behind the business object types. The word "light" is both
unfair and misleading. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial>Larry Hu</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2><FONT
face="Times New Roman" color=#000000 size=3></FONT></FONT></SPAN> </DIV>
<DIV dir=ltr align=left shape="_x0000_s1026">
<DIV><SPAN style="FONT-SIZE: 156%; text-shadow: auto"><SPAN
style="FONT-SIZE: 75%; COLOR: aqua; FONT-FAMILY: Wingdings">n</SPAN></SPAN></DIV></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu"
target=_blank>sap-wug-bounces@mit.edu</A> [mailto:<A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu" target=_blank>
sap-wug-bounces@mit.edu</A>] <B>On Behalf Of </B>Munday,Sherie
J.<BR><B>Sent:</B> Monday, May 08, 2006 2:21 PM<BR><B>To:</B> SAP Workflow
Users' Group<BR><B>Subject:</B> RE: WORKFLOW BEST
PRACTICES<BR></FONT><BR> </DIV></DIV>
<DIV style="DIRECTION: ltr"><SPAN class=e id=q_10b196b66969ec67_1>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2>Anjan,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>This
attachment is a high level summary that we did called Workflow 101. It
does not necessarily cover best practices, but you might find it useful.
The most important tip I would give anyone starting to develop workflows is to
make sure that the business process is well defined before you design the
workflow. If the process is not defined you will waste time and effort
chasing a moving target and the scope creep will be unbelievable!!
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>Best of
Luck,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2>Sherie</FONT></SPAN></DIV><BR>
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu"
target=_blank>sap-wug-bounces@mit.edu</A> [mailto:<A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug-bounces@mit.edu" target=_blank>
sap-wug-bounces@mit.edu</A>] <B>On Behalf Of </B>Rakshit, Anjan (CA -
Toronto)<BR><B>Sent:</B> Monday, May 08, 2006 12:34 PM<BR><B>To:</B> <A
onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:sap-wug@mit.edu"
target=_blank>sap-wug@mit.edu</A><BR><B>Subject:</B> WORKFLOW BEST
PRACTICES<BR></FONT><BR> </DIV>
<DIV></DIV>
<DIV>
<P><FONT face=Verdana size=3><SPAN lang=EN-GB
style="FONT-SIZE: 12pt; FONT-FAMILY: Verdana">Our client is requesting
information about the high-level policies, guiding principles, and governance
for Workflow used by other SAP users - particularly any high-tech
manufacturing organizations. The client is approaching initial design
and configuration of SAP and feel they need an overall governance strategy for
the implementation, change management, and on-going maintenance of Workflow.
</SPAN></FONT></P>
<P><FONT face=Verdana size=3><SPAN lang=EN-GB
style="FONT-SIZE: 12pt; FONT-FAMILY: Verdana"></SPAN></FONT> </P>
<P><FONT face=Verdana size=3><SPAN lang=EN-GB
style="FONT-SIZE: 12pt; FONT-FAMILY: Verdana">If anyone has a governance
document, best practices document or tips and tricks on workflow design for
SAP, it would be greatly appreciated. </SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks and
regards</SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P><B><I><FONT face=Arial color=blue size=2><SPAN lang=EN-GB
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: Arial">Anjan
Rakshit</SPAN></FONT></I></B><B><I><FONT face=Arial color=navy size=2> <SPAN
lang=EN-GB
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial"></SPAN></FONT></I></B></P></DIV></SPAN></DIV>
<DIV style="DIRECTION: ltr">
<P></P></DIV>
<DIV style="DIRECTION: ltr"><SPAN class=e id=q_10b196b66969ec67_3>
<HR SIZE=1>
<P></P><BR>
<P><STRONG><BR>*******************************************************************<BR>*******************<BR>Confidentiality
Warning: This message and any attachments are<BR>intended only for the use of
the intended recipient(s), are <BR>confidential, and may be privileged. If you
are not the intended<BR>recipient, you are hereby notified that any review,
retransmission,<BR>conversion to hard copy, copying, circulation or other use
of this<BR>message and any attachments is strictly prohibited. If you are not
<BR>the intended recipient, please notify the sender immediately by<BR>return
e-mail, and delete this message and any attachments from<BR>your system. Thank
you.<BR><BR>Information confidentielle: Le présent message, ainsi que tout
<BR>fichier qui y est joint, est envoyé à l'intention exclusive de<BR>son ou
de ses destinataires; il est de nature confidentielle et<BR>peut constituer
une information privilégiée. Nous avertissons<BR>toute personne autre que le
destinataire prévu que tout examen, <BR>réacheminement, impression, copie,
distribution ou autre<BR>utilisation de ce message et de tout fichier qui y
est joint est<BR>strictement interdit. Si vous n'êtes pas le destinataire
prévu,<BR>veuillez en aviser immédiatement l'expéditeur par retour de
<BR>courriel et supprimer ce message et tout document joint de
votre<BR>système.
Merci.<BR>*******************************************************************<BR>*******************<BR></STRONG></P></SPAN></DIV>
<DIV style="DIRECTION: ltr">
<DIV>
<P></P>
<P style="FONT-SIZE: x-small; FONT-FAMILY: Arial, Sans-Serif">This message is
for the designated recipient only and may contain privileged, proprietary, or
otherwise private information. If you have received it in error, please notify
the sender immediately and delete the original. Any other use of the email by
you is prohibited. </P></DIV>
<P></P></DIV><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"
target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>