<br><font size=2 face="sans-serif">Here is how we do it, I figured most
organizations on SAP would have something similar ... so much for figuring!</font>
<br>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="sans-serif">The standard transport path is from
DE to QE then from QE to PE/FE.</font>
<br>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="sans-serif">If you find this useful and need more
detail, I will be happy to provide.</font>
<br><font size=2 face="sans-serif"><br>
</font>
<table>
<tr>
<td><font size=3 color=#5f5f5f face="sans-serif">Berry Martin</font><font size=2 color=#5f5f5f face="sans-serif"><br>
IS Professional<br>
</font><font size=2 color=blue face="sans-serif"><u><br>
</u></font><a href=mailto:Berry.Martin@Milliken.com><font size=2 color=blue face="sans-serif"><u>Berry.Martin@Milliken.com</u></font></a><font size=2 color=#5f5f5f face="sans-serif"><br>
864.503.2261 office<br>
864.503.2444 fax<br>
864.923.3529 cell</font>
<tr>
<td><img src=cid:_2_090A8A5C090A865C00556FA685257715>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif"> </font><a href></a><font size=1 color=#5f5f5f face="sans-serif">
</font><a href></a><font size=1 color=#5f5f5f face="sans-serif">
</font></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">"Keohan, Susan - 1140 - MITLL"
<keohan@ll.mit.edu></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@MIT.EDU></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">04/30/2010 11:04 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">RE: workflow maintenance and enhancements</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">sap-wug-bounces@MIT.EDU</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Times New Roman">Hi Sue, Gayathri,</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">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. </font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">I was not taking that – the ‘upgrade
factor’ – into consideration. Call it selective amnesia.</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">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 </font><font size=3 face="Wingdings">J</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">Thanks for bringing me back to
reality on a Friday, </font>
<br><font size=3 face="Times New Roman">Sue</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Times New Roman">----</font>
<br><font size=2 face="Times New Roman">Susan R. Keohan</font>
<br><font size=2 face="Times New Roman">SAP Workflow Specialist</font>
<br><font size=2 face="Times New Roman">Enterprise Applications</font>
<br><font size=2 face="Times New Roman">Information Services Department</font>
<br><font size=2 face="Times New Roman">MIT Lincoln Laboratory</font>
<br><font size=2 face="Times New Roman">244 Wood Street, LI-200</font>
<br><font size=2 face="Times New Roman">Lexington, MA. 02420</font>
<br><font size=2 face="Times New Roman">781-981-3561</font>
<br><font size=2 face="Times New Roman">keohan@LL.MIT.EDU</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [</font><a href="mailto:sap-wug-bounces@mit.edu"><font size=2 face="Tahoma">mailto:sap-wug-bounces@mit.edu</font></a><font size=2 face="Tahoma">]
<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</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 color=#000080 face="Arial">Hi Sue,</font>
<br><font size=2 color=#000080 face="Arial"> </font>
<br><font size=2 color=#000080 face="Arial">I can understand Gayathri’s
issue.</font>
<br><font size=2 color=#000080 face="Arial"> </font>
<br><font size=2 color=#000080 face="Arial">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.</font>
<br><font size=2 color=#000080 face="Arial"> </font>
<br><font size=2 color=#000080 face="Arial">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.</font>
<br><font size=2 color=#000080 face="Arial"> </font>
<br><font size=2 color=#000080 face="Arial">There is no other way to do
that, is there?</font>
<br><font size=2 color=#000080 face="Arial"> </font>
<br><font size=2 color=#000080 face="Arial">Regards,</font>
<br><font size=2 color=#000080 face="Arial">Sue</font>
<br><font size=2 color=#000080 face="Calibri"> </font>
<div align=center>
<br>
<hr></div>
<br><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [</font><a href="mailto:sap-wug-bounces@mit.edu"><font size=2 face="Tahoma">mailto:sap-wug-bounces@mit.edu</font></a><font size=2 face="Tahoma">]
<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</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Times New Roman">Hi Gayathri,</font>
<br><font size=3 face="Times New Roman">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.</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">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.</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">Just my 2p,</font>
<br><font size=3 face="Times New Roman">Sue</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Times New Roman">----</font>
<br><font size=2 face="Times New Roman">Susan R. Keohan</font>
<br><font size=2 face="Times New Roman">SAP Workflow Specialist</font>
<br><font size=2 face="Times New Roman">Enterprise Applications</font>
<br><font size=2 face="Times New Roman">Information Services Department</font>
<br><font size=2 face="Times New Roman">MIT Lincoln Laboratory</font>
<br><font size=2 face="Times New Roman">244 Wood Street, LI-200</font>
<br><font size=2 face="Times New Roman">Lexington, MA. 02420</font>
<br><font size=2 face="Times New Roman">781-981-3561</font>
<br><font size=2 face="Times New Roman">keohan@LL.MIT.EDU</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [</font><a href="mailto:sap-wug-bounces@mit.edu"><font size=2 face="Tahoma">mailto:sap-wug-bounces@mit.edu</font></a><font size=2 face="Tahoma">]
<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</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">HI experts,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">What is the best way to handle simultaneously
fixes to a production workflow and also work on enhancements to the same
workflow ? </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Regards,</font>
<br><font size=2 face="Calibri">Gayathri</font>
<p><font size=3 color=red face="Times New Roman"><b><br>
Yazaki North America, Inc. - Confidentiality & Security Notice</b></font>
<div align=center>
<br>
<hr noshade></div>
<br><font size=3 face="Times New Roman">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.</font><tt><font size=2>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif"><br>
</font>
<hr><font size=2 face="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 </font><a href=www.milliken.com/terms><font size=2 face="Courier New">www.milliken.com/terms</font></a><font size=2 face="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>
***********************************************************************</font>
<br>
<br>