<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for the replies. Would using a newer version of the
workflow for enhancement and keeping the production version for fixes work ? How
does versioning affect transports. Can I maintain different transports for
different versions ? Will this be better than maintain 2 different templates ? In
our environment do not have a separate client to perform fixes.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Gayathri<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
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>Berry Martin<br>
<b>Sent:</b> Friday, April 30, 2010 11:34 AM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: workflow maintenance and enhancements<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Here is how we
do it, I figured most organizations on SAP would have something similar ... so
much for figuring!</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In ECC, we have
a DE (development), QE (quality assurance/testing), PE (production), and FE ( I
guess the F is for "fixes") clients.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The standard
transport path is from DE to QE then from QE to PE/FE.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>FE is a
redundant environment that is used solely for hot fixes. It is never accessed
by end users. It is solely for hot fixes that need to go directly to PE. Changes
to FE are only transported to PE and no other client. Any changes made to
FE requires incorporation into transports from DE or they will be lost.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>If you find
this useful and need more detail, I will be happy to provide.</span> <o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#5F5F5F'>Berry
Martin</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#5F5F5F'><br>
IS Professional<br>
</span><u><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><br>
</span></u><a href="mailto:Berry.Martin@Milliken.com"><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'>Berry.Martin@Milliken.com</span></a><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>
864.503.2261 office<br>
864.503.2444 fax<br>
864.923.3529 cell</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><img border=0 width=577 height=51 id="_x0000_i1025"
src="cid:image001.jpg@01CAEAAA.8DBE7690"><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'> </span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<br>
<br>
<o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>From:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Keohan,
Susan - 1140 - MITLL" <keohan@ll.mit.edu></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>To:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"SAP
Workflow Users' Group" <sap-wug@MIT.EDU></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Date:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>04/30/2010
11:04 AM</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Subject:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RE:
workflow maintenance and enhancements</span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#5F5F5F'>Sent by:</span> <o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>sap-wug-bounces@MIT.EDU</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" noshade style='color:gray' align=center>
</div>
<p class=MsoNormal><br>
<br>
<br>
Hi Sue, Gayathri, <br>
<br>
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. <br>
<br>
I was not taking that – the ‘upgrade factor’ – into consideration. Call
it selective amnesia. <br>
<br>
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 <span style='font-family:
Wingdings'>J</span> <br>
<br>
Thanks for bringing me back to reality on a Friday, <br>
Sue <br>
<br>
<span style='font-size:10.0pt'>----</span> <br>
<span style='font-size:10.0pt'>Susan R. Keohan</span> <br>
<span style='font-size:10.0pt'>SAP Workflow Specialist</span> <br>
<span style='font-size:10.0pt'>Enterprise Applications</span> <br>
<span style='font-size:10.0pt'>Information Services Department</span> <br>
<span style='font-size:10.0pt'>MIT Lincoln Laboratory</span> <br>
<span style='font-size:10.0pt'>244 Wood Street, LI-200</span> <br>
<span style='font-size:10.0pt'>Lexington, MA. 02420</span> <br>
<span style='font-size:10.0pt'>781-981-3561</span> <br>
<span style='font-size:10.0pt'>keohan@LL.MIT.EDU</span> <br>
<br>
<b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[</span><a href="mailto:sap-wug-bounces@mit.edu"><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>mailto:sap-wug-bounces@mit.edu</span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <b>On Behalf Of </b>Sue
Doughty<b><br>
Sent:</b> Friday, April 30, 2010 10:47 AM<b><br>
To:</b> 'SAP Workflow Users' Group'<b><br>
Subject:</b> RE: workflow maintenance and enhancements</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Hi
Sue,</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>I can
understand Gayathri’s issue.</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>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.</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>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.</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>There
is no other way to do that, is there?</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Regards,</span>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Sue</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:navy'> </span>
<o:p></o:p></p>
<p class=MsoNormal align=center style='text-align:center'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><br>
<b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
sap-wug-bounces@mit.edu [</span><a href="mailto:sap-wug-bounces@mit.edu"><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:sap-wug-bounces@mit.edu</span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <b>On Behalf Of </b>Keohan,
Susan - 1140 - MITLL<b><br>
Sent:</b> Friday, April 30, 2010 10:18 AM<b><br>
To:</b> SAP Workflow Users' Group<b><br>
Subject:</b> RE: workflow maintenance and enhancements</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
Hi Gayathri, <br>
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. <br>
<br>
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. <br>
<br>
Just my 2p, <br>
Sue <br>
<br>
<span style='font-size:10.0pt'>----</span> <br>
<span style='font-size:10.0pt'>Susan R. Keohan</span> <br>
<span style='font-size:10.0pt'>SAP Workflow Specialist</span> <br>
<span style='font-size:10.0pt'>Enterprise Applications</span> <br>
<span style='font-size:10.0pt'>Information Services Department</span> <br>
<span style='font-size:10.0pt'>MIT Lincoln Laboratory</span> <br>
<span style='font-size:10.0pt'>244 Wood Street, LI-200</span> <br>
<span style='font-size:10.0pt'>Lexington, MA. 02420</span> <br>
<span style='font-size:10.0pt'>781-981-3561</span> <br>
<span style='font-size:10.0pt'>keohan@LL.MIT.EDU</span> <br>
<br>
<b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
sap-wug-bounces@mit.edu [</span><a href="mailto:sap-wug-bounces@mit.edu"><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:sap-wug-bounces@mit.edu</span></a><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <b>On Behalf Of </b>Gayathri
Shivakumar<b><br>
Sent:</b> Friday, April 30, 2010 8:25 AM<b><br>
To:</b> sap-wug@mit.edu<b><br>
Subject:</b> workflow maintenance and enhancements</span> <br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>HI experts,</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>What is the
best way to handle simultaneously fixes to a production workflow and also work
on enhancements to the same workflow ? </span><br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Regards,</span>
<br>
<span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Gayathri</span>
<o:p></o:p></p>
<p><b><span style='color:red'><br>
Yazaki North America, Inc. - Confidentiality & Security Notice</span></b> <o:p></o:p></p>
<p class=MsoNormal align=center style='text-align:center'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" noshade style='color:gray' align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
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.<br>
<br>
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.<br>
<br>
Thank you.<tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>SAP-WUG mailing list</tt><br>
<tt>SAP-WUG@mit.edu</tt><br>
</span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span
style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
</span><br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
<br>
</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Courier New"'><br>
<br>
<br>
**** Confidentiality and Commercial Terms and Conditions Notice: *****<br>
Privileged/Confidential information may be contained in this message<br>
and is intended only for the use of the addressee. Please advise<br>
immediately if you or your employer do not consent to Internet e-mail<br>
for messages of this kind. If you are not the addressee, or person<br>
responsible for delivering to the person addressed, you may not copy or<br>
deliver this to anyone else. If you receive this message by mistake,<br>
please notify the sender immediately by return e-mail. All commercial<br>
transactions, offers and acceptances are exclusively subject/limited to<br>
and conditioned upon our terms posted at </span><a href="www.milliken.com/terms"><span
style='font-size:10.0pt;font-family:"Courier New"'>www.milliken.com/terms</span></a><span
style='font-size:10.0pt;font-family:"Courier New"'>,<br>
and we object to and reject any of your additional/different terms and<br>
conditions unless we expressly agree to them in a signed writing. <br>
Thank you.<br>
***********************************************************************</span> <o:p></o:p></p>
</div>
<p></p><p><br><font color=red size=3><b>Yazaki North America, Inc. - Confidentiality & Security Notice</b></font><hr noshade size=1 color=black>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.<br><br>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.<br><br>Thank you.</body>
</html>