<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Sue,<BR>
<BR>
<P dir=ltr style="MARGIN-RIGHT: 0px">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:</P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<P dir=ltr style="MARGIN-RIGHT: 0px"><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.</P>
<P dir=ltr style="MARGIN-RIGHT: 0px"> </P>
<P dir=ltr style="MARGIN-RIGHT: 0px">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.</P>
<P dir=ltr style="MARGIN-RIGHT: 0px"> </P>
<P dir=ltr style="MARGIN-RIGHT: 0px">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).</P>
<P dir=ltr style="MARGIN-RIGHT: 0px"> </P>
<P dir=ltr style="MARGIN-RIGHT: 0px">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...</P>
<P dir=ltr style="MARGIN-RIGHT: 0px"> </P>
<P dir=ltr style="MARGIN-RIGHT: 0px">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 iof 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.</P>
<P dir=ltr style="MARGIN-RIGHT: 0px"> </P>
<P dir=ltr style="MARGIN-RIGHT: 0px">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).</P></BLOCKQUOTE>
<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 stuff). 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>
<BR>
Regards,<BR>
<BR>
Mike GT<BR>
<HR id=stopSpelling>
<BR>
From: keohan@ll.mit.edu<BR>To: sap-wug@mit.edu<BR>Date: Wed, 5 Nov 2008 11:35:41 -0500<BR>Subject: ECC Upgrade - WF Transport Issues?<BR><BR><BR>
<STYLE>
.ExternalClass .EC_shape
{;}
</STYLE>
<STYLE>
</STYLE>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass span.EC_EmailStyle17
{font-family:'Times New Roman';color:windowtext;font-weight:normal;font-style:normal;text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.EC_Section1
{page:Section1;}
.ExternalClass ol
{margin-bottom:0in;}
.ExternalClass ul
{margin-bottom:0in;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">Hi All,</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">We are upgrading from 4.6c to ECC 6. </SPAN></FONT></P>
<P class=EC_MsoNormal><B><FONT face="Times New Roman" size=2><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 11pt">Some</SPAN></FONT></B><FONT size=2><SPAN style="FONT-SIZE: 11pt"> workflow definitions that were originally built in 4.6c have trouble when a corrected version is transported to QA.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">I am talking only about <B><SPAN style="FONT-WEIGHT: bold">definitions – not instances</SPAN></B>. </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">Here’s the long version…</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">WF Definition (originally built in 4.6c) in Development system (ECC 6) then transports to QA (ECC 6)</SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>1)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>Had errors in block structure, corrected via WF Builder (Extras> Special Functions> Block Correction</P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>2)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>Tranported to QA </P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>3)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>WF Definition was not updated in QA with first transport, header data did not reflect change version from date of first transport</P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>4)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>Transport logs ineffective (although they do report error 8)</P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>5)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>Generated new version in Dev. Transported to QA. No Transport errors</P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>6)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>New version ‘appears’ to be in QA</P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: -0.25in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><SPAN>7)<FONT face="Times New Roman" size=1><SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></FONT></SPAN></SPAN></FONT>Check on WF – SWUD In Dev:</P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><IMG id=EC__x0000_i1025 height=259 src="cid:image001.jpg@01C93F3A.A22756F0" width=444></SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">But in QA: (Workflow Definition does not exist????)</SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">:<IMG id=EC__x0000_i1026 height=318 src="cid:image002.jpg@01C93F3A.A22756F0" width=456></SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">8) PFTC_DIS In Dev (OK, warnings, but so what):</SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><IMG id=EC__x0000_i1027 height=410 src="cid:image003.jpg@01C93F3A.A22756F0" width=468></SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">In QA:</SPAN></FONT></P>
<P class=EC_MsoNormal style="TEXT-INDENT: 0.5in"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><IMG id=EC__x0000_i1028 height=389 src="cid:image004.jpg@01C93F3A.A22756F0" width=432></SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 11pt"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">I am scouring OSS Notes. We do get the warnings in QA when entering PFTC_DIS with various container elements (‘Container element TYPEID is not used’, Message No. WD315). So far notes seem to address elements *<B><SPAN style="FONT-WEIGHT: bold">missing</SPAN></B>* from the workflow containers (related to workflow instances, not definitions), Container elements missing (RSWF_CNT_BOR_ELEM_REPLACE), but this workflow was fine in Dev and the elements referred to do exist in QA… </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">Any tips would be appreciated.<BR>Thanks</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">Sue</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">----</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">Susan R. Keohan</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">SAP Workflow Specialist</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">Enterprise</SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 10pt"> Applications</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">Information Services Department</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">MIT Lincoln Laboratory</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">244 Wood Street</SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 10pt">, LI-200</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">Lexington</SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 10pt">, MA</SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 10pt">. 02420</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">781-981-3561</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 10pt">keohan@LL.MIT.EDU</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P></DIV><br /><hr />Read amazing stories to your kids on Messenger <a href='http://clk.atdmt.com/UKM/go/117588488/direct/01/' target='_new'>Try it Now!</a></body>
</html>