<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.search-highlight1
{mso-style-name:search-highlight1;
background:#FFFFCC;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Gayathri,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Workflow-versioning is definitely a good option when making
changes or enhancements to a process. Keep in mind that your workflow in
production references the active version at the start. This means when you
transport a new active version, your running processes still leverage the old
version while new processes are instantiated on the new active version. In the
case of an overwritten active version, your change has to be compliant with the
old version, if this is not the case, running workflows will run into an error.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I generally recommend a dual landscape for complex projects one
for the design, build and test as well the deploy phase of the project and the
other for parallel maintenance of the current applications. The below mentioned
Change and Request Management has been developed and introduced to support
distributed project and application management across different systems using
the Solution Manager and mechanisms such as retrofit and cross system object
locking.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(<a
href="http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/a3/0aae435a1342e8a56998d83a797161/frameset.htm">http://help.sap.com/saphelp_NW70EHP1core/helpdata/en/a3/0aae435a1342e8a56998d83a797161/frameset.htm</a>)<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>These mechanisms help you in your dual maintenance and are
designed to avoid inconsistencies in your project during cutover into
production. These mechanism “unfortunately” are also imposing some discipline
onto very creative people and often this is the hardest part when introducing
ChaRM.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So coming back to your initial question, I would make the
decision depending on whether there are incompatible changes to your workflow
and to whether there are running processes in your production system. Consider
also that version numbering can change when transporting an already existing
version into production.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For more details, just check the documentation below.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://help.sap.com/saphelp_NW70EHP1core/helpdata/de/c5/e4b7aa453d11d189430000e829fbbd/frameset.htm">http://help.sap.com/saphelp_NW70EHP1core/helpdata/de/c5/e4b7aa453d11d189430000e829fbbd/frameset.htm</a><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bodo<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Keohan, Susan - 1140 -
MITLL<br>
<b>Sent:</b> Dienstag, 4. Mai 2010 21:21<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: workflow maintenance and enhancements<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>See previous
discussions from Friday, April 30.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'><br>
…<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Tahoma","sans-serif";
color:black'>Change Request Management (</span><span class=search-highlight1><b><span
lang=EN-GB style='font-size:11.0pt;font-family:"Tahoma","sans-serif"'>Charm</span></b></span><span
lang=EN-GB style='font-size:11.0pt;font-family:"Tahoma","sans-serif";
color:black'>) functionality.</span><span lang=EN-GB style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:navy'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>… <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>----</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>Susan
R. Keohan</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>SAP
Workflow Specialist</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>Enterprise
Applications</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>Information
Services Department</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>MIT
Lincoln Laboratory</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>244
Wood Street, LI-200</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>Lexington,
MA. 02420</span><span lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'>781-981-3561</span><span
lang=EN-US style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;color:black'><a
href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a></span><span lang=EN-US
style='color:black'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Nat 4 Govender<br>
<b>Sent:</b> Tuesday, May 04, 2010 9:01 AM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Cc:</b> SAP Workflow Users' Group; sap-wug-bounces@mit.edu<br>
<b>Subject:</b> RE: workflow maintenance and enhancements<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p style='margin-bottom:12.0pt'><span lang=EN-US>Hi Jocelyn,<br>
<br>
Sorry to ask a silly question but what is the "</span><tt><span
lang=EN-US style='font-size:10.0pt'>CHARM transport process</span></tt><span
lang=EN-US>" ?<br>
</span><b><span lang=EN-US style='font-size:13.5pt;color:darkslateblue'><br>
Regards</span></b><span lang=EN-US style='font-size:13.5pt'><br>
Nat Govender<br>
Toyota South Africa<br>
IT - SAP Workflow Specialist<br>
Internal Ext. : 32645<br>
Direct Line : +27 031 910 2645<br>
Fax : 086 607 0414<br>
E-mail : </span><span lang=EN-US><a href="mailto:ngovender4@toyota.co.za"><span
style='font-size:13.5pt'>ngovender4@toyota.co.za</span></a></span><span
lang=EN-US style='font-size:13.5pt'><br>
<span style='color:fuchsia'><br>
If you tell the truth, you don't have to remember anything. </span></span><span
lang=EN-US><br>
</span><img border=0 width=16 height=16 id="Picture_x0020_1"
src="cid:image001.gif@01CAEE99.1DDD2680"
alt="Inactive hide details for "Dart, Jocelyn" <jocelyn.dart@sap.com>"><span
lang=EN-US>"Dart, Jocelyn" <<a href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>><o:p></o:p></span></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal style='margin-left:144.0pt'><b><span lang=EN-US
style='font-size:10.0pt'>"Dart, Jocelyn" <</span></b><b><span
style='font-size:10.0pt'><a href="mailto:jocelyn.dart@sap.com"><span
lang=EN-US>jocelyn.dart@sap.com</span></a></span></b><b><span lang=EN-US
style='font-size:10.0pt'>></span></b><span lang=EN-US style='font-size:
10.0pt'> </span><span lang=EN-US><br>
</span><span lang=EN-US style='font-size:10.0pt'>Sent by: </span><span
style='font-size:10.0pt'><a href="mailto:sap-wug-bounces@mit.edu"><span
lang=EN-US>sap-wug-bounces@mit.edu</span></a></span> <span lang=EN-US><o:p></o:p></span></p>
<p style='margin-left:144.0pt'><span style='font-size:10.0pt'>2010/05/04
01:38 AM</span> <o:p></o:p></p>
<table class=MsoNormalTable border=1 cellpadding=0 style='margin-left:144.0pt'>
<tr>
<td width=168 valign=top style='width:126.0pt;background:white;padding:
.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='text-align:center'><span lang=EN-US
style='font-size:10.0pt'>Please respond to<br>
"SAP Workflow Users' Group" <</span><span style='font-size:
10.0pt'><a href="mailto:sap-wug@mit.edu"><span lang=EN-US>sap-wug@mit.edu</span></a></span><span
lang=EN-US style='font-size:10.0pt'>></span><span lang=EN-US><o:p></o:p></span></p>
</td>
</tr>
</table>
</td>
<td width="60%" valign=top style='width:60.0%;padding:0cm 0cm 0cm 0cm'>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="1%" valign=top style='width:1.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=58 height=1 id="Picture_x0020_2"
src="cid:image002.png@01CAEE99.1DDD2680"
alt="cid:image002.png@01CAEE99.1DDD2680"><o:p></o:p></p>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:10.0pt'>To</span><o:p></o:p></p>
</td>
<td width="100%" valign=top style='width:100.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=1 height=1 id="Picture_x0020_3"
src="cid:image003.png@01CAEE99.1DDD2680"
alt="cid:image003.png@01CAEE99.1DDD2680"><span lang=EN-US><br>
</span><span lang=EN-US style='font-size:10.0pt'>"SAP Workflow Users'
Group" <</span><span style='font-size:10.0pt'><a
href="mailto:sap-wug@mit.edu"><span lang=EN-US>sap-wug@mit.edu</span></a></span><span
lang=EN-US style='font-size:10.0pt'>></span><span lang=EN-US><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="1%" valign=top style='width:1.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=58 height=1 id="Picture_x0020_4"
src="cid:image002.png@01CAEE99.1DDD2680"
alt="cid:image002.png@01CAEE99.1DDD2680"><o:p></o:p></p>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:10.0pt'>cc</span><o:p></o:p></p>
</td>
<td width="100%" valign=top style='width:100.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=1 height=1 id="Picture_x0020_5"
src="cid:image003.png@01CAEE99.1DDD2680"
alt="cid:image003.png@01CAEE99.1DDD2680"><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="1%" valign=top style='width:1.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=58 height=1 id="Picture_x0020_6"
src="cid:image002.png@01CAEE99.1DDD2680"
alt="cid:image002.png@01CAEE99.1DDD2680"><o:p></o:p></p>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:10.0pt'>Subject</span><o:p></o:p></p>
</td>
<td width="100%" valign=top style='width:100.0%;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=1 height=1 id="Picture_x0020_7"
src="cid:image003.png@01CAEE99.1DDD2680"
alt="cid:image003.png@01CAEE99.1DDD2680"><span lang=EN-US><br>
</span><span lang=EN-US style='font-size:10.0pt'>RE: workflow maintenance
and enhancements</span><span lang=EN-US><o:p></o:p></span></p>
</td>
</tr>
</table>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td width=58 valign=top style='width:43.5pt;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=1 height=1 id="Picture_x0020_8"
src="cid:image003.png@01CAEE99.1DDD2680"
alt="cid:image003.png@01CAEE99.1DDD2680"><o:p></o:p></p>
</td>
<td width=336 valign=top style='width:252.0pt;padding:0cm 0cm 0cm 0cm'>
<p class=MsoNormal><img border=0 width=1 height=1 id="Picture_x0020_9"
src="cid:image003.png@01CAEE99.1DDD2680"
alt="cid:image003.png@01CAEE99.1DDD2680"><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p></o:p></p>
</td>
</tr>
</table>
<p style='margin-bottom:12.0pt'><span lang=EN-US><br>
</span><tt><span lang=EN-US style='font-size:10.0pt'>Hi Sue,</span></tt><span
lang=EN-US style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>For something like this we would usually use parallel environments and use
the CHARM transport process to sort it out.</tt><br>
<tt>Essentially to control/automate the synchronization process as much as
possible.</tt><br>
<tt>This is one of those... "go talk to the basis guys" answers -
sorry.</tt><br>
<tt>Regards,</tt><br>
<tt>Jocelyn</tt><br>
<br>
<tt>________________________________</tt><br>
<tt>From: sap-wug-bounces@mit.edu [sap-wug-bounces@mit.edu] On Behalf Of
Keohan, Susan - 1140 - MITLL [keohan@ll.mit.edu]</tt><br>
<tt>Sent: Saturday, 1 May 2010 12:56 AM</tt><br>
<tt>To: SAP Workflow Users' Group</tt><br>
<tt>Subject: RE: workflow maintenance and enhancements</tt><br>
<br>
<tt>Hi Sue, Gayathri,</tt><br>
<br>
<tt>I do understand this dilemma – we go thru it every time we upgrade or apply
major support packs. We get a ‘prime’ Dev environment in which we do
production support, and then we get the upgrade environment in which we do
enhancements. It’s a beast.</tt><br>
<br>
<tt>I was not taking that – the ‘upgrade factor’ – into consideration.
Call it selective amnesia.</tt><br>
<br>
<tt>As far as I know copying the WFs and trying to keep both versions in sync
is the only way to do this. Of course, in my own perfect little world
(imaginary) we would not have to do this kind of thing :)</tt><br>
<br>
<tt>Thanks for bringing me back to reality on a Friday,</tt><br>
<tt>Sue</tt><br>
<br>
<tt>----</tt><br>
<tt>Susan R. Keohan</tt><br>
<tt>SAP Workflow Specialist</tt><br>
<tt>Enterprise Applications</tt><br>
<tt>Information Services Department</tt><br>
<tt>MIT Lincoln Laboratory</tt><br>
<tt>244 Wood Street, LI-200</tt><br>
<tt>Lexington, MA. 02420</tt><br>
<tt>781-981-3561</tt><br>
<tt><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a></tt><br>
<br>
<tt>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>]
On Behalf Of Sue Doughty</tt><br>
<tt>Sent: Friday, April 30, 2010 10:47 AM</tt><br>
<tt>To: 'SAP Workflow Users' Group'</tt><br>
<tt>Subject: RE: workflow maintenance and enhancements</tt><br>
<br>
<tt>Hi Sue,</tt><br>
<br>
<tt>I can understand Gayathri’s issue.</tt><br>
<br>
<tt>I’m currently working on a six month project that involves changes to the
system done by another group, plus workflow changes to an existing workflow.
While this six month project is going on we need to have a path to
production to be able to send fixes (if they occur) for the existing workflow
while we are in development on the project.</tt><br>
<br>
<tt>The only way I knew to do that was to make a copy of the existing workflow
in which I am making the project changes. If any fixes need to be done
before the project goes to PRD, I’ll have to make changes in both workflows to
keep everything in sync. It is challenging.</tt><br>
<br>
<tt>There is no other way to do that, is there?</tt><br>
<br>
<tt>Regards,</tt><br>
<tt>Sue</tt><br>
<br>
<tt>________________________________</tt><br>
<tt>From: sap-wug-bounces@mit.edu [<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>]
On Behalf Of Keohan, Susan - 1140 - MITLL</tt><br>
<tt>Sent: Friday, April 30, 2010 10:18 AM</tt><br>
<tt>To: SAP Workflow Users' Group</tt><br>
<tt>Subject: RE: workflow maintenance and enhancements</tt><br>
<br>
<tt>Hi Gayathri,</tt><br>
<tt>I would not try to simultaneously fix productive workflows and also do
enhancements – unless you are planning on all of these corrections/enhancements
going to the same place at the same time. Personally, I would fix the
issue with production, transport up, and then generate a new version of the
workflow in your Dev environment and begin the enhancements.</tt><br>
<br>
<tt>Having said that, you could, of course, copy the productive workflow to
another workflow template, allowing you to do the fixes in the original
template, and the enhancements in the copied template. I would hate to
have to coordinate that development effort though.</tt><br>
<br>
<tt>Just my 2p,</tt><br>
<tt>Sue</tt><br>
<br>
<tt>----</tt><br>
<tt>Susan R. Keohan</tt><br>
<tt>SAP Workflow Specialist</tt><br>
<tt>Enterprise Applications</tt><br>
<tt>Information Services Department</tt><br>
<tt>MIT Lincoln Laboratory</tt><br>
<tt>244 Wood Street, LI-200</tt><br>
<tt>Lexington, MA. 02420</tt><br>
<tt>781-981-3561</tt><br>
<tt><a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a></tt><br>
<br>
<tt>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[<a href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</a>]
On Behalf Of Gayathri Shivakumar</tt><br>
<tt>Sent: Friday, April 30, 2010 8:25 AM</tt><br>
<tt>To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a></tt><br>
<tt>Subject: workflow maintenance and enhancements</tt><br>
<br>
<tt>HI experts,</tt><br>
<br>
<tt>What is the best way to handle simultaneously fixes to a production
workflow and also work on enhancements to the same workflow ?</tt><br>
<br>
<tt>Regards,</tt><br>
<tt>Gayathri</tt><br>
<br>
<tt>Yazaki North America, Inc. - Confidentiality & Security Notice</tt><br>
<br>
<tt>________________________________</tt><br>
<tt>This email is intended only for the person or entity to which it is
addressed and may contain confidential, proprietary and/or privileged material.
Any review, distribution, reliance on, or other use of this information by
persons or entities other than the intended recipient is prohibited. If you
receive this message in error, please immediately notify the sender and delete
it and all copies of it from your system.</tt><br>
<br>
<tt>Visitors are prohibited from taking pictures or video at anytime in YNA or
its affiliated company facilities unless prior authorization is obtained from
facilities management.</tt><br>
<br>
<tt>Thank you.</tt><br>
<br>
<tt>_______________________________________________</tt><br>
<tt>SAP-WUG mailing list</tt><br>
<tt><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></tt><br>
<tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></tt></span><span
lang=EN-US><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>******************************************************************
This e-mail is a privileged and private communication and may be read, copied
and used only by the intended recipient(s). If you are not an intended
recipient, please inform the sender by return e-mail with the subject heading
"Received in error". Please then delete the e-mail; destroy any
copies of it and do not disclose its contents to any person or entity. If you
are not the intended recipient, note that any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is strictly prohibited
and may be unlawful. Neither the sender nor Toyota South Africa Motors (Pty)
Ltd accepts any liability whatsoever as a result of the further dissemination
of this e-mail. Toyota South Africa Motors (Pty) Ltd does not guarantee that
e-mail communications are secure or error-free, as information could be
intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or
contain viruses.
******************************************************************<o:p></o:p></span></p>
</div>
</body>
</html>