<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2900.2523" name=GENERATOR>
<STYLE>@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=#606420 link=blue>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><FONT
face=Arial>Sherie:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><FONT
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><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 class=529522113-09052006><FONT
face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><FONT
face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><FONT face=Arial>Larry
Hu</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=529522113-09052006><FONT face=Arial
color=#0000ff size=2><FONT face="Times New Roman" color=#000000
size=3></FONT> </DIV>
<DIV dir=ltr align=left v:shape="_x0000_s1026">
<DIV class=O
style="mso-line-spacing: '90 20 0'; mso-margin-left-alt: 216; mso-char-wrap: 1; mso-kinsoku-overflow: 1"><SPAN
style="FONT-SIZE: 156%; FONT-FAMILY: 'Times New Roman'; text-shadow: auto"><SPAN
style="FONT-SIZE: 75%; LEFT: -4.25%; COLOR: aqua; FONT-FAMILY: Wingdings; POSITION: absolute; TOP: 0.3em; mso-special-format: bullet; mso-color-index: 3">n</SPAN></SPAN></DIV></DIV></FONT></SPAN><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>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>
<DIV dir=ltr align=left><SPAN class=275131418-08052006><FONT face=Arial
color=#0000ff size=2>Anjan,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=275131418-08052006><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 class=275131418-08052006><FONT face=Arial
color=#0000ff size=2>Best of Luck,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=275131418-08052006><FONT face=Arial
color=#0000ff size=2>Sherie</FONT></SPAN></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>Rakshit, Anjan (CA -
Toronto)<BR><B>Sent:</B> Monday, May 08, 2006 12:34 PM<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> WORKFLOW BEST PRACTICES<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><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.
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Verdana size=3><SPAN lang=EN-GB
style="FONT-SIZE: 12pt; FONT-FAMILY: Verdana"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><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.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks and
regards<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><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"><o:p></o:p></SPAN></FONT></I></B></P></DIV>
<P>
<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><div id="##disclaimer##"><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></BODY></HTML>