<br><font size=2 face="sans-serif">Sandy,</font><br><br><font size=2 face="sans-serif">I'm sorry I cannot answer your specific
questions below (I only have intermediate WF skillz). However, each
of your points sounds reasonable and shouldn't take too long to check and
see if it is necessary once you have an upgraded test system to work with.
The real experts here can probably provide you with better feedback.</font><br><br><font size=2 face="sans-serif">I only wanted to make the point that
we upgraded to ECC 6.0 roughly 1.5 years ago, and many of our workflows
were trainwrecks afterward. In fact it was at that point that I really
learned workflow as just about every custom workflow we use broke after
the upgrade. Granted I work in a heavily customized environment (the
land of 'Z'...) so I don't think this was so much a problem with SAP products,
but of our own making. Incidentally, we didn't seem to have any problems
with pure out-of-the-box SAP supplied workflows (which we mostly use in
HR).</font><br><br><font size=2 face="sans-serif">In any case, from my own experience
(if I ever had to do this again), I would:</font><br><font size=2 face="sans-serif">1. Pay particular attention to agent
determination, especially if you are using custom agent determination rules
and techniques</font><br><font size=2 face="sans-serif">2. Seperate testing for new workflow
instances versus existing instances (those workflow instances that already
are running at the time of the upgrade). Most of the problems we
experienced were with already-running workflows - of which there were hundreds.</font><br><br><font size=2 face="sans-serif">The 2 areas where we experienced the
most problems were with travel approval and incoming invoice processing,
which for us, are almost entirely custom everything (objects, events, programs,
you name it...).</font><br><br><font size=2 face="sans-serif">Just a friendly FYI, nothing more.<br></font><font size=4 color=#808000><b> </b></font><p><font size=4 color=#808000><b>Michael McLey</b></font><font size=3 color=#808000><b></b><br>MBUSI - IT Parts & Administration </font><font size=2 color=#808000><br>Mercedes-Benz US International, Inc.</font><font size=3 color=#808000></font><font size=2 color=#808000><br>1 Mercedes Drive</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>Vance, AL 35490</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>PHONE: (205) 462 - 5239</font><font size=3 color=#808000> </font><font size=2 color=#808000><br>EMAIL: michael.mcley@daimler.com</font><font size=3 color=#808000>
</font><br><br><br><table width=100%><tr valign=top><td width=40%><font size=1 face="sans-serif"><b>sandysydney@gmail.com</b></font><br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font><p><font size=1 face="sans-serif">11/01/2010 07:20 PM</font><table border><tr valign=top><td bgcolor=white><div align=center><font size=1 face="sans-serif">Please respond to<br>sap-wug@mit.edu</font></div></table><br><td width=59%><table width=100%><tr valign=top><td><div align=right><font size=1 face="sans-serif">To</font></div><td><font size=1 face="sans-serif">sap-wug@mit.edu</font><tr valign=top><td><div align=right><font size=1 face="sans-serif">cc</font></div><td><tr valign=top><td><div align=right><font size=1 face="sans-serif">Subject</font></div><td><font size=1 face="sans-serif">Workflow Upgrade 4.6C to ECC6 - manual
settings during Cutover & Version</font></table><br><table><tr valign=top><td><td></table><br></table><br><br><br><font size=2 face="Arial">Hello Guys,<br><br>We are upgrading to ECC 6 from 4.6C and we are on release 701 & support
pack SAPKB70106.<br><br>I would like to know which are the "<b>Manual activities</b>"
that needs to done during cutover and <b>WHEN</b> should these should be
done (eg. before ECC6 upgade, or after ECC6 upgrade but before config/dev
transports, or after config/dev transports).<br><br>I have looked on few threads and found the following info. Please correct
me or add extra info if i have missed something:<br><br>1. Configure RFC destination & other mandatory options in
Transaction SWU3.<br>2. Run Transaction SWU_OBUF to clear the runtime buffers before users start
Testing.<br><br>I assume rest of changes would be imported with transports, but i have
read through lot of SDN threads that <b>all custom Workflow definitions
needs to be ACTIVATED in each system (DEV - QAS- PRD)</b> and <b>custom
BOR objects needs be REGENERATED in each system (DEV - QAS- PRD).</b> Also,
do I have manually <b>set the agent assignement for Customer Task as GENERAL
TASK</b> in each system? Are above stated 3 steps needs to be manually
done in each system or transports take care of them ? I am bit confused.
Could anybody please advise me regarding the <b>Manual Task/activities
that needs to done in each system during cutover during WF upgrade from
4.6 C to ECC6.</b><br><br>Thanks for posting excellent stuff regarding the Workflow Upgrades on this
mailing list. It really helped me in resolving most of my issues.<br><br>Thanks in advance<br><br>Kind Regards<br><br></font><br><br><font size=3><i>Regards</i> </font><br><br><font size=3><b><i>Sandy</i></b></font><br><font size=3><i> </i></font><br><br><tt><font size=2>_______________________________________________<br>SAP-WUG mailing list<br>SAP-WUG@mit.edu<br>http://mailman.mit.edu/mailman/listinfo/sap-wug<br></font></tt><br><font face="sans-serif"><font face="sans-serif, Arial, Helvetica" size="-1" color="#808080"><br>If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.
<br></br>
</font></font>