<div>Thanks Edwin for all your tips.. they will definitley help in my upgrade quest. </div>
<div>I remember discussing this subject with you at the ASUG as well. We have 40+ customised workflows in all different functional areas of SAP and testing has always been a key in all our tech upgrades, SP etc. I will make a note to begin review of OSS notes ahead of time.
</div>
<div> </div>
<div>Regards</div>
<div>Shalini <br> </div>
<div><span class="gmail_quote">On 6/8/06, <b class="gmail_sendername">Edwin Mukusha</b> <<a href="mailto:emukusha@nebraska.edu">emukusha@nebraska.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><br><font face="sans-serif" size="2">Hi Shalini,</font> <br><br><font face="sans-serif" size="2">Here's a presentation that we did for this past ASUG that could give you some clues on an approach to answer your questions. We upgraded from
4.6C to 4.7 and we found out that a lot had changed in this seemingly small step. Our lessons from our upgrade were that; </font><br><br><font face="sans-serif" size="2">- yes, you do need lots of time to play with the new version in sandbox environment preferably with your own configuration
</font> <br><font face="sans-serif" size="2">- you need to review all oss notes on the subject</font> <br><font face="sans-serif" size="2">- review all release notes for each basis level. (for example 4.6C, 4.6D, 6.10, 6.20
, 6.40 etc), this might seem a bit much but it certainly gave us a better appreciation/understanding on how the new functionality came about</font> <br><font face="sans-serif" size="2">- the new xml based container had a wide ranging implications
</font> <br><font face="sans-serif" size="2">- allow enough time to do test test test test test. single unit testing, full integration testing, end-user testing, formalize your testing by documenting all your tests</font>
<br><font face="sans-serif" size="2">- don't allow workflow to be solely the responsibility of the workflow team separate to the business/functional transaction or processes. If for example HR hires a person and workflow was supposed to be triggered, make it clear that this process is not fully tested or working until the workflow process is fully accounted for
</font> <br><br><font face="sans-serif" size="2">The actual impact on your workflows is going depend obviously on how many you have and also how much customization you have. So in short you need a firm understanding of new functionality offered in your target release from a technical point of view which will in turn allow you to gauge how big or small your upgrade will be.
</font> <br><br><font face="sans-serif" size="2">I hope this helps and good luck,</font> <br><br><br><br><font face="sans-serif" size="2">--------------------------------------------------------------------------<br>Edwin Mukusha
<br>Administrative Systems Group</font> <br><font face="sans-serif" size="2">Business Technologies Lead<br>University of Nebraska<br>Phone: (402) 472-7756 Fax: (402) 472-7390 <br>Email: <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:emukusha@nebraska.edu" target="_blank">
emukusha@nebraska.edu</a> <br>--------------------------------------------------------------------------<br></font><br><br><br><br><br>
<table width="100%">
<tbody>
<tr valign="top">
<td width="40%"><font face="sans-serif" size="1"><b>"Shalini Sabnani" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:shalini.sabnani@gmail.com" target="_blank">shalini.sabnani@gmail.com
</a>></b> </font><br><font face="sans-serif" size="1">Sent by: <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a></font>
<p><font face="sans-serif" size="1">06/08/2006 01:09 PM</font>
<table border="1">
<tbody>
<tr valign="top">
<td bgcolor="white">
<div align="center"><font face="sans-serif" size="1">Please respond to<br>"SAP Workflow Users' Group" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a>></font></div></td></tr></tbody></table><br></p>
<td width="59%">
<table width="100%">
<tbody>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
<td><font face="sans-serif" size="1"><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a></font>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div>
<td>
<tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
<td><font face="sans-serif" size="1">Workflow in ECC 6.0</font></td></td></tr></td></td></tr></td></td></tr></tbody></table><br>
<table>
<tbody>
<tr valign="top">
<td>
<td></td></td></tr></tbody></table><br></td>
<td><p></p></td></td></tr></tbody></table></div>
<div><span class="e" id="q_10bb54a6480ec0b0_1"><br><br><br><font size="3">Folks,</font> <br><font size="3">I understand from various Workflow groups that there is a lot of change in SAP Workflow going from 4.6C to ECC 6.0
or even ECC 5.0. What I would like to understand is what is this lot of change ? Has the functionality (what workflow can do) changed or has the way it is code and designed change. Would it be safe to assume that Workflow in ECC will continue to do what it does in
4.6C at the minimum. In an upgrade scenario (4.6c - ECC5.0) should a lot of time be planned for upgrades of Workflow ?</font> <br><font size="3">If any one has links articles, whitepages etc on the above or would like share their own upgrade experience I would be very keen to read/ hear the same.
</font> <br><font size="3"> </font> <br><font size="3">Thanks is advance for you assistance with the above.</font> <br><font size="3">Shalini Sabnani</font> <br><font size="3"> </font> <br></span></div>
<div><font size="3">~~Necessity is the Mother of Invention.. </font><tt><font size="2">_______________________________________________<br>SAP-WUG mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:SAP-WUG@mit.edu" target="_blank">
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></font></tt><br>
</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><br clear="all"></blockquote></div><br><br clear="all"><br>-- <br>~~Necessity is the Mother of Invention..