<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=windows-1255">
<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:"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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:HouschkaBold;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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";}
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";}
p.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9, li.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9, div.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9
{mso-style-name:ecxa4cf2f35-85f1-416d-928f-c600a8d649f9;
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";}
p.ecxa4cf2f35-85f1-416d-928f-c600a8d649f91, li.ecxa4cf2f35-85f1-416d-928f-c600a8d649f91, div.ecxa4cf2f35-85f1-416d-928f-c600a8d649f91
{mso-style-name:ecxa4cf2f35-85f1-416d-928f-c600a8d649f91;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4, li.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4, div.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4
{mso-style-name:ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4;
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";}
p.ecxa4cf2f35-85f1-416d-928f-c600a8d649f92, li.ecxa4cf2f35-85f1-416d-928f-c600a8d649f92, div.ecxa4cf2f35-85f1-416d-928f-c600a8d649f92
{mso-style-name:ecxa4cf2f35-85f1-416d-928f-c600a8d649f92;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b41, li.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b41, div.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b41
{mso-style-name:ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b41;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:0cm;
margin-left:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecx552134512-14012010
{mso-style-name:ecx552134512-14012010;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1743211855;
mso-list-type:hybrid;
mso-list-template-ids:627219438 -1316617440 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Andy,<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'>As you might have seen there is a note which mentions this cross-release
transport<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=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![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'>1175535 - Cross-release transport of workflows<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'>It states that it is not supported but is possible and gives
some hits (Basic hints).<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'>Anyway, you seem to have got the activation under control. If any
other issues crop up just let us know.<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>
<div>
<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>Catherall,
Andy<br>
<b>Sent:</b> 15 January 2010 20:53<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Transporting workflows from 4.6c to ECC6?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Thanks Mike </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>[For a moment there, I thought Jocelyn had answered my query too
:-( ]</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>An update for those searching in the future.</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>After a lot more digging, I have found the following:</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>The warnings in the 'IMPORT' area of the transport log are probably
red herrings. I think SAP is handling the different table sizes correctly and
is just...um... <em><span style='font-family:"Arial","sans-serif"'>warning</span></em>
me about it.</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>This lead me to the view that my workflow data <em><span
style='font-family:"Arial","sans-serif"'>is</span></em> in our ECC6 Dev
environment. The workflows have just not activated correctly/at all...</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I then noticed that those workflows that have not activated
seemed to also be missing a couple of areas in the Transport Log. The CHECK
VERSION and METHODS entries were not there. Did this mean that the FM
rh_activate_wfobject_after_imp etc was not being called?</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I have confirmed that the appropriate entries appear in SOBJ for
PDWS objects, so I am not sure why the AFTER IMPORT features do not appear to
be running. <u>Anyone got any ideas?</u> They are either running and failing
silently (nothing in the log or ST22), or they are not running at all. Yet
the transport thinks it was successful, except for this minor act of
activating.</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Back to the workflows. I have further discovered that in SWDSHEADER,
the 9999 versions of those failed workflows had exactly the change
data I was missing. So, how to run the 'activation' process, as if we'd just
transported? (SWUD and viewing the templates were insufficient, as they were
only opening the 'old' version).</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I further discovered that the fantastic Mr Eddie Morris had
answered this question way back in early 2007 (<a
href="http://mailman.mit.edu/pipermail/sap-wug/2007-January/024840.html">http://mailman.mit.edu/pipermail/sap-wug/2007-January/024840.html</a>)</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>This led me to OSS note 981295, which in turn describes how to
use program RSWD_REPLICATE_FROM_9999.</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>And so now we appear to have active workflows at the correct
versions! A little more testing and analysis will be required to check that all
associated objects & linkages are peachy, but we're in a much better place
than a few days ago.</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>So, just the question regarding the AFTER IMPORT functionality
remaining.</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Thanks wuggers!</span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Andy</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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>Mike Gambier<br>
<b>Sent:</b> Thursday 14 January 2010 13:25<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> RE: Transporting workflows from 4.6c to ECC6?</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Andy,<br>
<br>
The short answer is mostly 'yes', but sometimes (typically where ECC 6
wants to deal with new tables) also 'no'.<br>
<br>
The longer answer is probably more like this:<br>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>RE:
ECC Upgrade - WF Transport Issues?</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>þ</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
From: </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> on behalf of
Keohan, Susan (<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>) <br>
Sent: 06 November 2008 15:54:52 <br>
To: SAP Workflow Users' Group (<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>)
<br>
5 attachments | Download all attachments (115.9 KB) <br>
image001.jpg (22.6 KB), image002.jpg (16.8 KB), image003.jpg (42.3 KB),
image004.jpg (34.1 KB), ATT00001 (0.1 KB) <br>
<br>
Hi Mike, All potential upgraders!<br>
<br>
Well, I did find this helpful – <br>
<a
href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1">https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1</a><br>
<br>
In particular, there is one OSS Note (1068627) which is good because it lists a
lot of notes that may be helpful.<br>
We are on Basis Support Pack 15, so a lot of them did not apply to us.<br>
I’ve filled out an OSS Message. SAP did respond advising me to check: <br>
* 1175535 - Cross-release transport of workflows<br>
If you look at section [5] of note 1098805 there are some points<br>
I would like you to check. They are:<br>
Troubleshoot versions & activation<br>
- Do the Source and Target systems have the same system date &<br>
time?<br>
- If you created any new container elements in your workflow can<br>
you make sure that the their data references also exist in the<br>
QA system.<br>
- Did you create any new tasks and add them to the workflow in<br>
the development system. If so please make sure that you also<br>
transported the task to the quality system.<br>
- Have you checked transaction SWDM -> Extras -> Transported<br>
workflows in the target system? It will show up in red if<br>
there are any issues.<br>
* 1098805 - Troubleshooting Tips & Tricks for workflow issues<br>
<br>
Additionally, table SWDSHEADER, for version 9999 of the workflow, should have
the exact date and time stamp as the same entry in your Dev Box.<br>
Many thanks to Eddie Morris for helping me get this far.<br>
<br>
So far, no other resolution. I’ve deleted offending container elements in
Dev, re-added them, checked binding, re-transported, all to no avail.<br>
I’ll keep you posted.<br>
Sue<br>
----<br>
Susan R. Keohan<br>
SAP Workflow Specialist<br>
Enterprise Applications<br>
Information Services Department<br>
MIT Lincoln Laboratory<br>
244 Wood Street, LI-200<br>
Lexington, MA. 02420<br>
781-981-3561<br>
<a href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</a><br>
<br>
--------------------------------------------------------------------------------<br>
From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[mailto:sap-wug-bounces@mit.edu] On Behalf Of Mike Gambier<br>
Sent: Wednesday, November 05, 2008 12:27 PM<br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
Subject: RE: ECC Upgrade - WF Transport Issues?<br>
<br>
Hi Sue,<br>
<br>
We're at the tail-end of a long protracted code merge between 4.6c and ECC 6
and our experiences of the whole WF Transport area are these:<br>
<br>
1. SAP categorically does NOT support transporting 4.6c changes to ECC 6
definitions. And from what we've been told they never will either, despite our
complaints that they need to consider they're existing customers who can't just
upgrade overnight.<br>
<br>
2. SAP expects clients to upgrade their definitions once and once only. And
therefore their migration tools and programs are written to update the new
tables from the 'old' tables once and once only.<br>
<br>
3. Basically speaking you have to assume that most changes to containers and
container elements will NOT be Transportable and will have to be manually
applied directly in ECC 6. Thankfully, binding changes seem to be unaffected
for the most part although there too some things have crept in that might catch
you because of unicode parsing (there's new syntax added by SWDD for type
definitions that you can't add in 4.6c).<br>
<br>
4. Some brand new WF Definition features have to be defaulted but these values
may not be ideal for you. For instance we have chosen to stick to the 'old'
STRUCTURE PERSISTENCE conatiner tables (SWW_CONTOB) but we need to explicitly
state this in the WF Definition header settings otherwise furture versions may
decide to switch to the new tables (Compatiblity setting). And we've found that
on occasion 4.6c Transports have a nasty habit of re-initialising some of these
defaults...<br>
<br>
5. Dummy nodes in ECC 6 cause havoc until a Block Correction is carried out, as
you have found out. These go away but come back if you re-import from 4.6c of
course. Nice! The fault is deep down in the new logic for determining step
types and the fact that ECC 6 adds an extra piece of data somewhere to define a
dummy block that you can't transport.<br>
<br>
6. Multi-line tables now have to be handled with a brand new container element
that 4.6c can't deal with. That was a fun one to work out. You actually have to
hack your binding in text editor mode to insert the new syntax if you
want to pacth this kind of thing up (WFParForEach).<br>
<br>
The Transport mechanism in 4.6c can only succeed in delivering changes where
the tables in ECC 6 have remained in place and are still in use. Thankfully
this means that in most cases the changes to actual step logic and binding does
make it through, but be careful where the new logic being added is based on new
container elements (see 3). <br>
<br>
To be fair I appreciate SAP's dilemma a bit because the jump from 4.6c to ECC 6
in terms of Workflow is subtle but huge. The addition of XI/PI/BPM (whatever
they call it now) and the whole revamp of the Workflow engine in ABAP Classes
has meant a complete rethink in a lot of key areas. <br>
<br>
But I think clients are currently faced with a painful choice at the moment
which leaves a sour taste in my mouth to be honest. They either send Transports
through and patch things up manually (as we have had to do) or they carry out
parallel changes and keep their development codestreams apart (at the risk of
missing stu! ff). Either way the upgrade becomes quite a pain if you use
Workflow a lot.<br>
<br>
By the way, be aware that the tables for Event Linkages have also changed, so
SWETYPV is based on a completely different table view and hence Transports from
4.6c are utterly useless.<br>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
Regards,<br>
<br>
Mike GT<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Subject: Transporting workflows from 4.6c
to ECC6?<br>
Date: Thu, 14 Jan 2010 06:03:44 -0700<br>
From: andy.m.catherall@cadbury.com<br>
To: sap-wug@mit.edu<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>Hi</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>Is it possible to [successfully]
transport 4.6c workflow developments (esp. WS objects) to ECC6? </span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>We still have our 4.6c
path-to-production, and we have our parallel ECC6 project landscape for the
upgrade. Some urgent changes/fixes have been made to a few of our production
workflows, and these transports have been cloned back into our ECC6 Dev &
Sandbox systems.</span></span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>That has not gone well... :o(</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>We have noticed two key features:</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>1) In most cases, the WS objects are
not activating. There is no error, nor any clear warning explaining why not.</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>2) In most cases, we have seen
warnings along the following lines:</span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'> different
nametabs for table HRS1212</span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'> different
nametabs for table SWBRULECOU</span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
<span class=ecx552134512-14012010> etc.</span><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>Clearly, the 'new' tables are of a
different size to the 4.6c tables, hence the offsets are incorrect. </span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>However, in at least one example
- involving two WS templates - the activations </span></span><em><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>did</span></em><span
class=ecx552134512-14012010><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
occur despite the warnings.</span></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>So, is there evidence/experience of
successful transports of this nature out there, and I just need to find the
appropriate correction or fix? Or, is this approach impossible?</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>I further note that we are only on
SAPKB70103 - 4,5 & 6 exist, so I am working my way through these notes to
see if there are any solutions. For example, note 1276795 may help, though
it does not sound ideal. </span><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span class=ecx552134512-14012010><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>Thanks again, guys!</span></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"HouschkaBold","serif";
color:blue'>Andy Catherall</span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'> <br>
</span><span style='font-size:10.0pt;font-family:"HouschkaBold","serif";
color:blue'>Technical Analyst - SAP Workflow, IXOS & DMS</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'><img
border=0 width=80 height=32 id="_x0000_i1027"
src="cid:image001.gif@01CA9829.9AD371B0"></span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Int:
751 0556</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<br>
</span><span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Ext:
+44 (0)121 486 0556</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<br>
</span><span style='font-size:7.5pt;font-family:"HouschkaBold","serif"'>Mobile:
+44 (0)7813 025481</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><b><span lang=EN-GB style='font-size:10.0pt;font-family:
"Verdana","sans-serif";color:maroon'>The Cadbury Cocoa Partnership is working
to secure the future of cocoa farming around the world. Cadbury Dairy Milk bars
are now Fairtrade certified in the UK and Ireland. Visit </span></b><b><u><span
lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:blue'><a href="http://www.cadbury.com/" title="http://www.cadbury.com/">www.cadbury.com</a></span></u></b><b><span
lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:maroon'> to learn more.</span></b><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><b><span lang=EN-GB style='font-size:10.0pt;font-family:
"Verdana","sans-serif";color:green'>Be part of our "Purple Goes
Green" commitments and don't print this email.</span></b><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>-----------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>This
email (including any attachment) is confidential and may contain privileged
information and is intended for the use of the individual(s) to whom it is
addressed. If you are not the intended recipient or receive it in error, you
may not use, distribute, disclose or copy any of the information contained
within it and it may be unlawful to do so. If you are not the intended
recipient please notify us immediately by returning this email to us at <u><span
style='color:blue'><a href="mailto:mailerror@cadbury.com">mailerror@cadbury.com</a></span></u>
and destroy all copies.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Any
views expressed by individuals within this email do not necessarily reflect the
views of Cadbury Holdings Ltd or any of its subsidiaries or affiliates. This
email does not constitute a binding offer, acceptance, amendment, waiver or
other agreement, or create any obligation whatsoever, unless such intention is
clearly stated in the body of the email. Whilst we have taken reasonable steps
to ensure that this email and any attachments are free from viruses, recipients
are advised to subject this email to their own virus checking, in keeping with
good computing practice. We accept no liability for any damage sustained as a
result of any viruses. Please note that email received by Cadbury Holdings Ltd
or its subsidiaries or affiliates may be monitored in accordance with
applicable law. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>This
email originates from Cadbury Holdings Ltd ("Cadbury") or Cadbury UK
("Cadbury UK") as the case may be.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Cadbury
Holdings Ltd: registered in England and Wales, registered no. 52457<br>
Registered office address: Cadbury House, Sanderson Road, Uxbridge,
Middlesex, UB8 1DH United Kingdom. <span style='color:black'>Telephone: +44
(0)1895 615000 Fax:+44 (0)1895 615001 </span><br>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Cadbury
UK: a partnership of Cadbury UK Ltd, Trebor Bassett Ltd and The Old Leo Company
Ltd. each of which is registered in England and Wales. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Principal trading address: Cadbury
House, Sanderson Road, Uxbridge, Middlesex, UB8 1DH United Kingdom. <span
style='color:black'>Telephone: +44 (0)1895 615000 Fax:+44 (0)1895 615001
</span><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>-----------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Got
a cool Hotmail story? <a href="http://clk.atdmt.com/UKM/go/195013117/direct/01/"
target="_new">Tell us now</a> <o:p></o:p></span></p>
</div>
</body>
</html>