<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)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 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;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1233616534;
mso-list-template-ids:967870204;}
@list l1
{mso-list-id:1861704547;
mso-list-type:hybrid;
mso-list-template-ids:1831265306 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Sandy,<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In answer to your questions.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[1] Versions do not have to be the same across all your systems.
When you make a change DEV and transport to QAS it will check if there are
active work items for that workflow. If there are then it will create a new
version so the active work items can complete with the current version and the
new work items will use the newly transported version. (Same applies when you
transport to PRD).<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[2] Pushing users to complete work items before the upgrade is
only a suggestion and does not have to completed at all. You should not have
many issues with your work items but some points to look out for are:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Container elements based on table fields that no longer exist.
When you try to execute these work items they will go into error. After you
upgrade and before your users start executing work items I would suggest you look
at note 1058159 and run report RSWDVERCNT. This identifies any issues in your
workflow templates and gives you the option to change the container definition.
Note 939489 also deals with this issue.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span
style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If you use structures in your workflow definitions/containers
and they have been changed (e.g. the index of the fields in the structure moves)
then note 910573 can help here. You need to run report RSWF_MIG_CONTAINER_STRUCTS.
The note details how and when to use it.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[3] If nothing is imported after transporting initially and you
have refreshed the buffers in the target system then it sounds like there was a
problem activating the new workflow version in the target system. There are
some notes related to this but I guess you will be upgrading to the latest
support pack so you should have all of these notes. It can also happen if you
have failed to transport a new object to the target system first. E.g. if you create
a new task and insert it into your workflow and then transport the workflow to
the target system it will not activate because the task does not yet exist in
the target system. Please transport all new objects (Tasks, custom reference
structures/tables, object attributes/methods) to the target system before you
transport the workflow definition.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I hope this helps.<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>
<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'>Eddie<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><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 0cm 0cm 0cm'>
<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>Sandy<br>
<b>Sent:</b> 05 November 2010 02:38<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> Impact of WF Versions on Transports during Upgrade from 4.6 C
to ECC 6<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><em><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks
a lot Susan & Micheal for your suggestions regarding WF Cutover upgrade
activities. </span></em> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><em><span style='font-family:"Arial","sans-serif"'>Much
appreciated</span></em><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><em>I have some further queries regarding Impact of WF
Versions on Transports during Upgrade from 4.6 C to ECC 6</em><o:p></o:p></p>
</div>
<ol start=1 type=1>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><em>What if changes are made to WF
definition in current DEV system and Imported to PRD system, then WF
in PRD system would have one version (Plus) higher than the version
of the WF definition in Current DEV upgrade system (Since DEV upgrade system
is a Copy of PRD system). So when Transports would be imported to PRD from
DEV->Quality - >PRD, is there any possibilty of conflict due to
difference in Versions? Or transport would simpley overwrite the current
version in PRD from one imported from DEV->QAS->. If there is a
conflict? How could we resolve it?</em><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><em>If the client is not able to push the users
to complete all the work item generated from 4.6 C workflow definition
before Upgrading the PRD to ECC 6, what could be the
impact? I mean ?What sort of errors could be experienced while executing
the old Work items in ECC6 environment if there is not much Change in
container or definition change.There are about 100
Custom Workflow and heaps of Work items in Client system. I dont
think they can actually process all the work items.</em><o:p></o:p></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
mso-list:l0 level1 lfo1'><em>Also, I have read in many threads that "
No changes were imported in QAS from DEV when transports were
imported the FIRST time" Then REIMPORTING the transports again
second time brought in the changes to QAS. Did anyone knows a reason for this?</em><o:p></o:p></li>
</ol>
<p><em>Thanks a lot for your valuable suggestions</em><o:p></o:p></p>
<div>
<p class=MsoNormal><em>Regards</em><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><b><i>Sandy</i></b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>On 3 November 2010 03:29, <<a
href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal>Send SAP-WUG mailing list submissions to<br>
<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a
href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu"
target="_blank">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sap-wug-owner@mit.edu"
target="_blank">sap-wug-owner@mit.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br>
<br>
Today's Topics:<br>
<br>
1. RE: Workflow Upgrade 4.6C to ECC6 - manual settings during<br>
Cutover & Version (Keohan,
Susan - 1140 - MITLL)<br>
<br>
<br>
---------- Forwarded message ----------<br>
From: "Keohan, Susan - 1140 - MITLL" <<a
href="mailto:keohan@ll.mit.edu" target="_blank">keohan@ll.mit.edu</a>><br>
To: "SAP Workflow Users' Group" <<a
href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>
Date: Tue, 2 Nov 2010 12:29:01 -0400<br>
Subject: RE: Workflow Upgrade 4.6C to ECC6 - manual settings during
Cutover & Version<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>Hi Michael, Sandy,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>Excellent questions, excellent points.</span><o:p></o:p></p>
<p><span style='color:black'>1)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>I run SWU3 in each environment as it becomes
available to schedule the background jobs, assign the WF Admin, etc.
Takes less than 10 minutes – should be done in Dev,QA,PRD after the upgrade,
when Basis allows you in.</span><o:p></o:p></p>
<p><span style='color:black'>2)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>Sure, run SWU_Obuf – or wait for the
Cinderella Effect (past midnight, everything gets refreshed)</span><o:p></o:p></p>
<p><span style='color:black'>3)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>I do generate each BOR object after the
upgrade as I go from Dev – QA – PRD, after Checking them first!</span><o:p></o:p></p>
<p><span style='color:black'>4)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>SWUD on each workflow – test environment –
Consistency check for components (including subworkflows) should help you sort
the wheat from the chaff as well.</span><o:p></o:p></p>
<p><span style='color:black'>5)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>Agent assignments for General Tasks are
transportable, I believe, but my Basis friends let me do it ‘the workflow
way’. Then they shut me out.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>Michael, I sympathize! I had heard from another
organization about WF Train Wrecks – and in our case, we were fortunate that we
were able to encourage our users to complete almost all workitems prior to the
upgrade. Since we had upgraded from EBP 3.5 to SRM 5.0 Extended Classic
just 1.5 years prior, our users were sympathetic to this, and weekly reports
provided them with insight as to how many outstanding workflows they had.
However, we are a relatively small shop – although our workflow footprint
is quite large. We have no SAP-delivered workflows running,
but plenty of custom ones. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>You do need to:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p><span style='color:black'>1</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>The first bullet in the SAP document does say
‘Complete all running workflow instances’ - So really try to convince
your business people of this. You can, if necessary, report on workflows
in process at the time of the upgrade, and perhaps kill them, and manually
start new workflows after the upgrade? As I said, it depends on your
business.</span><o:p></o:p></p>
<p><span style='color:black'>2</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>Check each custom workflow – you will probably
need to do ‘Block Correction’ on each one. You will probably have more
DDIC and binding corrections too – which goes right back to #1.</span><o:p></o:p></p>
<p><span style='color:black'>3)</span><span style='font-size:7.0pt;color:black'>
</span><span style='color:black'>Absolutely test previously started (if you
must) and freshly-started (after upgrade) workflows as you move
thru Dev and QA. This will help you prepare for the oncoming train </span><span
style='font-family:Wingdings'>J</span><span style='color:black'>. You
will probably be able to form a plan for addressing any workflows that look as
though they are going south – and this will almost certainly be the ones that
were running prior to upgrade. It’s also helpful to document
each test - which workflow acted flukey, what the resolution was, so you
can refer back to it, and share it with your other WF folks.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>If you do read and use the document (upgrading SAP Business
Workflow from SAP 4.6c to SAP ERP 6.0) please do rate it – it is only when
people see that e-learnings are used and helpful that they are encouraged to
create more. Which is a good thing for all of us! </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'><a
href="http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1"
target="_blank">http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1</a></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>----</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Susan R. Keohan</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>SAP Workflow Specialist</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Enterprise Applications</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Information Services Department</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>MIT Lincoln Laboratory</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>244 Wood Street, LI-200</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>Lexington, MA. 02420</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'>781-981-3561</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:black'><a href="mailto:keohan@LL.MIT.EDU"
target="_blank">keohan@LL.MIT.EDU</a></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>
[mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>]
<b>On Behalf Of </b><a href="mailto:michael.mcley@daimler.com" target="_blank">michael.mcley@daimler.com</a><br>
<b>Sent:</b> Tuesday, November 02, 2010 10:20 AM<br>
<b>To:</b> <a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a><br>
<b>Subject:</b> Re: Workflow Upgrade 4.6C to ECC6 - manual settings during
Cutover & Version</span><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
<span style='font-size:10.0pt'>Sandy,</span><br>
<br>
<span style='font-size:10.0pt'>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.</span><br>
<br>
<span style='font-size:10.0pt'>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).</span><br>
<br>
<span style='font-size:10.0pt'>In any case, from my own experience (if I ever
had to do this again), I would:</span><br>
<span style='font-size:10.0pt'>1. Pay particular attention to agent
determination, especially if you are using custom agent determination rules and
techniques</span><br>
<span style='font-size:10.0pt'>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.</span><br>
<br>
<span style='font-size:10.0pt'>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...).</span><br>
<br>
<span style='font-size:10.0pt'>Just a friendly FYI, nothing more.</span><o:p></o:p></p>
<p style='margin-bottom:12.0pt'><b><span style='font-size:13.5pt;color:olive'>Michael
McLey</span></b><span style='color:olive'><br>
MBUSI - IT Parts & Administration </span><span style='font-size:10.0pt;
color:olive'><br>
Mercedes-Benz US International, Inc.<br>
1 Mercedes Drive</span><span style='color:olive'> </span><span
style='font-size:10.0pt;color:olive'><br>
Vance, AL 35490</span><span style='color:olive'> </span><span style='font-size:
10.0pt;color:olive'><br>
PHONE: (205) 462 - 5239</span><span style='color:olive'> </span><span
style='font-size:10.0pt;color:olive'><br>
EMAIL: <a href="mailto:michael.mcley@daimler.com" target="_blank">michael.mcley@daimler.com</a></span><span
style='color:olive'> </span><o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:7.5pt'><a href="mailto:sandysydney@gmail.com" target="_blank">sandysydney@gmail.com</a></span></b><br>
<span style='font-size:7.5pt'>Sent by: <a
href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a></span><o:p></o:p></p>
<p><span style='font-size:7.5pt'>11/01/2010 07:20 PM</span><o:p></o:p></p>
<table class=MsoNormalTable border=1 cellpadding=0>
<tr>
<td valign=top style='background:white;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=center style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;text-align:center'><span style='font-size:7.5pt'>Please respond to<br>
<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a></span><o:p></o:p></p>
</td>
</tr>
</table>
</td>
<td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
<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 align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;text-align:right'><span style='font-size:7.5pt'>To</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><span style='font-size:7.5pt'><a href="mailto:sap-wug@mit.edu"
target="_blank">sap-wug@mit.edu</a></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;text-align:right'><span style='font-size:7.5pt'>cc</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;text-align:right'><span style='font-size:7.5pt'>Subject</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto'><span style='font-size:7.5pt'>Workflow Upgrade 4.6C to ECC6 - manual
settings during Cutover & Version</span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
</table>
</td>
</tr>
</table>
<p><br>
<br>
<br>
<span style='font-size:10.0pt'>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>
</span><br>
<br>
<i>Regards</i> <br>
<br>
<b><i>Sandy</i></b><br>
<i> </i><br>
<br>
<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><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a></tt><br>
<tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></tt><br>
</span><br>
<span style='font-size:10.0pt;color:gray'><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. </span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>