<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecx868155315-09122009
{mso-style-name:ecx868155315-09122009;}
p.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b86, li.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b86, div.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b86
{mso-style-name:ecx7588a79e-a56e-4eb5-807e-a8a2451b6b86;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b861, li.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b861, div.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b861
{mso-style-name:ecx7588a79e-a56e-4eb5-807e-a8a2451b6b861;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxc6d3c6c6-5c23-4132-8928-8063b150774c, li.ecxc6d3c6c6-5c23-4132-8928-8063b150774c, div.ecxc6d3c6c6-5c23-4132-8928-8063b150774c
{mso-style-name:ecxc6d3c6c6-5c23-4132-8928-8063b150774c;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b862, li.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b862, div.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b862
{mso-style-name:ecx7588a79e-a56e-4eb5-807e-a8a2451b6b862;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxc6d3c6c6-5c23-4132-8928-8063b150774c1, li.ecxc6d3c6c6-5c23-4132-8928-8063b150774c1, div.ecxc6d3c6c6-5c23-4132-8928-8063b150774c1
{mso-style-name:ecxc6d3c6c6-5c23-4132-8928-8063b150774c1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b863, li.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b863, div.ecx7588a79e-a56e-4eb5-807e-a8a2451b6b863
{mso-style-name:ecx7588a79e-a56e-4eb5-807e-a8a2451b6b863;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxc6d3c6c6-5c23-4132-8928-8063b150774c2, li.ecxc6d3c6c6-5c23-4132-8928-8063b150774c2, div.ecxc6d3c6c6-5c23-4132-8928-8063b150774c2
{mso-style-name:ecxc6d3c6c6-5c23-4132-8928-8063b150774c2;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxecx156511519-08122009
{mso-style-name:ecxecx156511519-08122009;}
span.ecxecx562264707-09122009
{mso-style-name:ecxecx562264707-09122009;}
span.ecxecx968284307-09122009
{mso-style-name:ecxecx968284307-09122009;}
span.ecxecxecgmailquote
{mso-style-name:ecxecxec_gmail_quote;}
span.ecxecxece
{mso-style-name:ecxecxec_e;}
span.EmailStyle32
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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'>That Alon guy is a cowboy. No wonder he lives in Texas!<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Imagine that! Reusing an SAP delivered data element. Will the horrors
ever cease….<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>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Alon Raskin</span></b><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>e:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'> <b><a href="mailto:araskin@3i-consulting.com"
title="mailto:araskin@3i-consulting.com blocked::mailto:araskin@3i-consulting.com">araskin@3i-consulting.com</a></b></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#1F497D'><o:p></o:p></span></p>
</div>
<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 0in 0in 0in'>
<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>Mike
Gambier<br>
<b>Sent:</b> Wednesday, December 09, 2009 10:32 AM<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> RE: Workflow Upgrade issues (4.6c to ECC 6)<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Andy,<br>
<br>
The surgery was required on the Workflow Container definitions themselves,
specifically where non-existent Data Dictionary types were discovered to be the
root cause of some abnormal behaviour.<br>
<br>
We found that we had live WF instances of some definitions that
compiled just fine pre-upgrade that all of a sudden fell over in ECC 6
because they wanted to use some data elements/fields that had simply
vanished because of the upgrade. <br>
<br>
In our case the things that went missing were actually in SAP's
namespace so we couldn't stop them from disappearing, i.e. some of our WF
developers (*ahem* Alon Raskin, not mentioning any names of course!) had made
use of an old SAP data type that ended up being zapped from DDIC.<br>
<br>
So let's just say that a few 'adjustments' (direct hacks) needed to
be made post-upgrade to some SAP tables like SWDSBINDEF (specifically
fields REFSTRUCT & REFFIELD) to allow the errored WFs to be restarted
and 'find' the correct data type to use going forward.<br>
<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: RE: Workflow Upgrade issues (4.6c
to ECC 6)<br>
Date: Wed, 9 Dec 2009 09:01:33 -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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Thanks Mike</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>I'm still unclear on a
fundamental point:</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'>"...although we did have to
perform a few surgical procedures on a few definitions to resolve the odd bug
here and there. And for the record we did NOT kill all of our active instances
at all. "</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>These two statements appear
to be mutually exclusive (unless I am *really* missing something).</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=ecx868155315-09122009><u><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>A typical scenario</span></u></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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* We have some WF_1
instances running version_1 on a 4.6c PROD machine</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* We take a copy of prod
(for test purposes)</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* We test these running instances
of WF_1 and find a bug... lets say, in the bindings.</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* We make a fix to resolve
this issue in our ECC6 landscape. WF_1 has been reactivated and a transport
created.</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* ...</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* Some time later, we
finally go live. The production environment is upgraded and the 'fix'
transports are uploaded.</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>* The active instances of
WF_1 at version_1 (which started just prior to the upgrade) will run into
the bug. Any new instances will now start version_2, and hence be bug-free
(hopefully!).</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Where did the surgical
procedures take place such that active instances were able to continue after
the upgrade? In the 4.6c environment, in advance of the upgrade?</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Thanks again</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=ecx868155315-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Andy</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 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> Wednesday 09 December 2009 14:30<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> RE: Workflow Upgrade issues (4.6c to ECC 6)</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"'>Hi
Andy,<br>
<br>
I'm glad you found the thread useful :)<br>
<br>
Several months on from the upgrade and I'm pleased to say we've made the
transition to an ECC 6 platform without too much fallout, so in the
immortal words on the HG2G book "Don't Panic!". <br>
<br>
Nothing went drastically wrong, although we did have to perform a few surgical
procedures on a few definitions to resolve the odd bug here and there. And for
the record we did NOT kill all of our active instances at all. Instead we had
millions of them waking up and playing with the new Workflow engine code
reasonable natively. The only ones that had problems 'wakng up' were typically
ones that were trying to invoke standard SAP Functions that had been zapped in
during the upgrade, e.g. SWW_BI_EXECUTE_S_NEW.<br>
<br>
Probably the best thing you can do is scan through <strong><span
style='font-family:"Verdana","sans-serif"'>OSS Note 1068627</span></strong> and
prepare for some thorough testing prior to the big day.<br>
<br>
Provided you don't intend to import Workflow definition changes from a 4.6c (or
earlier) system into an ECC 6 one <u>on a continuous basis</u>, as we did, you
should find your definitions probably only need to be looked at a couple of
times before they bed down. You might want to create 'new' versions in your
development environments just to be sure you can differentiate between new
instances and old ones but it wasn't actually necessary in most cases. Just
good practice really.<br>
<br>
Perhaps the biggest concern we had (and continue to have) is the use of the XML
container and the persistence profile at our volumes. Simply put, we have not
switched to the new tables at all. Mostly because we rely heavily on being able
to 'find' objects in Workflow containers for exception and monitoring processes
and so need stuff to still be in SWW_CONTOB. All of which means we have
religiously set our Persistence Profile to the 'Structured' setting which
forces the code to use the 'old' container tables.<br>
<br>
Having said that our PI system is merrily using ccBPM stuff (essentially that
means Workflow) and is using the XML Container tables, albeit at
significantly lower volumes.<br>
<br>
Pretty soon we'll complete the holy trinity and have Workflows running in our
new SAP CRM 7.0 system too. Which will mean WF-BATCH whizzing along in 3
different SAP systems and 3 different ABAP codestacks all at the same time. Oh
joy... :)<br>
<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=ecxstopSpelling>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Subject: RE: Workflow Upgrade issues (4.6c
to ECC 6)<br>
Date: Wed, 9 Dec 2009 05:56:13 -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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Hi all</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Apologies for resurrecting
an old thread... I'm working my way through all the upgrade-lesson posts, as we
are now finally moving from 4.6c to ECC6. I too have recognised this "Do I
*really* have to end all my workflow instances/business processes!?!"
dilemma, and am trying to understand the subtle</span></span><span
class=ecxecx562264707-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>ties</span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> behind
it. This thread seemed a very pertinent place to ask my question</span></span><span
class=ecxecx562264707-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>s</span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>.</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>I really appreciate all the
lessons which have been put on this forum with respect to WF upgrades... from
this, I get the strong impression that there may be a multitude of bugs, issues
and associated corrections to workflow definitions, bindings, the 'block structure'
etc, in support of ECC6. I am witnessing a number of these issues in our test
environment, and they are impacted both in-flight instances & new
instances.</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Many of these fixes will
result in new versions of the workflow design: So, for example, if I
identify & fix a binding issue in my ECC6 test environment, I will have to
re-activate the workflow and promote the change into production at cut-over.
This instantly means that any workflows might be in-progress during the
cut-over weekend will be not be 'valid' in the new environment, because they
will not be running the corrected version. Further, we may have to change an
object or method such that old versions of the workflow cannot successfully
call it... Again, in-flight workflow instances are the living-dead; we know
they will not continue after the upgrade.</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>That all made sense to me
and my little understanding of the universe... and I can foresee having to
forewarn the business of this. They will by very impressed, I'm sure!</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>However, there are hints in
th</span></span><span class=ecxecx968284307-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>is thread - and other
similar</span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> </span></span><span
class=ecxecx968284307-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>ones - </span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>of people
somehow managing to cajole their workflow instances into continuing across the
upgrade boundary...</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>So, my question</span></span><span
class=ecxecx968284307-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>s</span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>:</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Where </span></span><span
class=ecxecx968284307-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>are </span></span><span class=ecxecx156511519-08122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>all the
fixes made such that 'old' versions of the workflows were still functional
even after the upgrade?</span></span><span class=ecxecx968284307-09122009><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> Can they
all be made in the 4.6c system, in advance of the upgrade?</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=ecxecx968284307-09122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>How are all the fixes
made? If they cannot all be made in the 4.6c environment (e.g. the
corrected block-structure issue</span></span><span
class=ecxecx562264707-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'> only manifests in ECC6</span></span><span
class=ecxecx968284307-09122009><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>), how are new versions avoided?</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Many thanks for this
information.</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=ecxecx156511519-08122009><span style='font-size:
10.0pt;font-family:"Arial","sans-serif";color:blue'>Andy</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>
<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 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 31 July 2008 11:59<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> RE: Workflow Upgrade issues (4.6c to ECC 6)</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><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"'>Hi,<br>
<br>
Just a follow-up on my earlier post. Feel free to ignore if you're not bothered
about upgrading from 4.x to 700+.<br>
<br>
After a welcome visit from the SAP Gods of Workflow (Ralf Goetzinger and
Peter Amrhein) we now have a couple of freshly issued OSS Notes to help us
along with our quest:<br>
<br>
1. 1234971 - Workflow Builder: Changing the ParForEach expression syntax
(essentially tweaks the SAP Upgrade FM SWD_UPGRADE_3XX_TO_4XX) which should fix
our Multiline binding issues. Yay :)<br>
<br>
2. 1228836 - Compatibility of conditions with date/time constants (provides an
alternative binding solution for active instances of 'old' definitions at
runtime). Does not actually fix the WF Definition and add the new required
{TYPE=...} syntax, but could be a life-saver during an upgrade if dates and
time bindings are used a lot. Also provides a rather useful ABAP Report
utility to scrutinise your WF Definitions and sniff out date/time bindings
(RSWDCLRBUF) which, if you copy and clone, you can adjust to examine other
binding types as well :)<br>
<br>
Anybody else going through an upgrade should find these two notes particularly
useful.<br>
<br>
These can also be found attached to the composite Upgrade Note 1068627 which is
starting to read a bit like a bible...<br>
<br>
Ralf and Peter, if you're reading this, thanks again!<br>
<br>
Regards,<br>
<br>
Mike GT <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 style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
Date: Fri, 20 Jun 2008 10:09:04 +1000<br>
From: paul.batey@presenceofit.com.au<br>
To: sap-wug@mit.edu<br>
Subject: Re: Workflow Upgrade issues (4.6c to ECC 6)<br>
<br>
<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hi
Mike,<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"'>A
client of mine just went from 46B to ECC6, and we found the following workflow
problems:<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"'>1)
Every workflow had to have a block correction done in workflow builder
(this may fix your par for each error). Run SWU7 and if you get loads of
invalid node type errors, a block correction will fix it.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>2)
Old FORMHTML.PROCESS steps short dumped, so we replaced them with the shiny new
form step.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>3)
Workflow versions were completely butchered when transported from the first
upgraded box to the next in the sequence. This was fixed by running FM
SWD_WFD_REPLICATE_FROM_9999 and putting the WSXXXXXXXX number into the IM_TASK
field.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>4)
We used customised versions of RSWUWFML to send email notifications of
workitems. This and any other custom program that put entries into the
SOST queue (email, fax etc) did not properly commit (if memory serves me an
SO_OFFICE_SEND exception 1 error in SOST). A simple explicit COMMIT WORK
statement at the appropriate place in each program sorted that one out.<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"'>Apart
from that, there were minimal issues with workflows starting before the upgrade
and finishing afterwards (unless they hit the short dumping form step)<br>
<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=ecxecxecgmailquote><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>On 6/18/08, <b>Mike Gambier</b> <<a
href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</a>> wrote:</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:"Verdana","sans-serif"'>Gijs,<br>
<br>
We will have millions of active instances running when we bring the system down
to upgrade it. There's no way we will be able to shut them down and restart,
despite the SAP white paper suggesting that we really should. We have about 100
WF definitions to check...<br>
<br>
Consequently we're having to test how well they perform in an upgraded
environment before we do it for real. Which means testing lots of areas:
triggering events event queued or otherwise & binding (which works
differently in ECC 6), deadlines (different again in ECC 6), event listeners
(which are shifted to a completely different table), complex alternate
bindings, dialog work items being executed & terminating events, forks,
loops, dynamic steps and, of course, general tRFC/ARFCSSTATE/feedback errors.<br>
<br>
Whilst it's always nice to see new OO stuff coming through as part of the
upgrade, the new versions of the Workflow service jobs are proving to be a bit
hard to predict in how they do things. So we're waiting to see how they cope at
volume too.<br>
<br>
By the time we go live we'll have gone through several full blown upgrade
simulations. All of which means a lot of effort. Hence the pain...<br>
<br>
That and 4 High Priority OSS Messages already and you can see where I'm coming
from. Still, it's educational and quite fun to dig around in the new
stuff :)<br>
<br>
MGT<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"'>From:
<a href="mailto:gijs@houtzagers.com">gijs@houtzagers.com</a><br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
Subject: RE: Workflow Upgrade issues (4.6c to ECC 6)<br>
Date: Tue, 17 Jun 2008 18:46:25 +0200 <o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span class=ecxecxece><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Hi Mike,</span><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:navy'>Could you elaborate on the painful stuff you were confronted by?</span><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:navy'>Regards</span><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:navy'> </span><o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Gijs Houtzagers</span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><br>
</span><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Principal Consultant</span></i><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> </span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Kirkman</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> Company B.V.</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Amsterdamsestraatweg 40</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>3743 DT Baarn</span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><br>
</span><span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>The Netherlands</span><span style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><br>
</span><span lang=NL style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:navy'> </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><b><span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>T</span></b><span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'> +31 (0)88 40 40 400</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><b><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>F</span></b><span lang=EN-GB style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:navy'> +31 (0)88 40 40 499</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><a href="http://www.kirkmancompany.com/">www.kirkmancompany.com</a></span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='color:navy'> </span><span lang=EN-GB
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>------------------------------------------------------</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>The information contained in this message </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>may be confidential and is intended to be </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>exclusively for the addressee. Should you </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>receive this message unintentionally, you are </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>kindly requested not to make any use </span><span style='font-size:
10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>whatsoever of the contents. Please notify</span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>the sender by return e-mail and delete </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>the material from any computer.</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
</span><span lang=NL style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>---------------------------------------------------- </span><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='color:navy'> </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:"Arial","sans-serif";
color:navy'> </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'>
<hr size=2 width="100%" align=center>
</div>
<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"'> <a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] <b>On Behalf
Of </b>Mike Gambier<br>
<b>Sent:</b> dinsdag 17 juni 2008 17:12<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Workflow Upgrade issues (4.6c to ECC 6)</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>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>Hi,<br>
<br>
We're currently struggling through a rather painful upgrade process from 4.6c
to ECC 6 and we've hit a few Workflow mines.<br>
<br>
Despite several high priority OSS Messages the end result from SAP so far as
been a fairly poor acknowledgement of issues that need to be addressed
manually, culminating in OSS Note 1175535.<br>
<br>
Basically we have 4 known faults at the moment. Two relating to changes
not coming across from 4.6c into ECC 6 based around Workflow Container Elements
and Event Linkages, which I can quite understand as the target tables ahve
shifted in ECC 6. But the other two point to problems in SAP's 'mapping'
process where they convert 4.6c (or older) definitions into ECC 6 syntax
(Kernel 700+).<br>
<br>
These issues are:<br>
<br>
1. Multiline Table handling - to use these properly in loops and dynamic steps
it seems you now have to use a new &WF_PARFOREACH_INDEX& element that
only becomes available after 4.6c<br>
<br>
They did suggest trying a dodgy binding switch as implemented by OSS
Message 1083317, which mostly works for active instances but only as long
as the 'Change Release' value on the WF version remains equal to or lower than
'46C'. Not all that useful if the instances are on the current active version
and that definition is then activated in the ECC 6 environment. But that
doesn't actually fix the definition syntax going forward anyway.<br>
<br>
2. Condition binding after 4.6c introduces a {TYPE=...} additional statement in
SWDSCONDEF so that, for example, a hard-coded string like '31.12.9999' can
be converted into a date variable at runtime to compare against an object date
property. Prior to 4.6c this statement did not exist. Now it is required or
else the binding is considered to be erroneous and a syntax error will result.<br>
<br>
Has anyone esle come across upgrade-related issues other than these?<br>
<br>
Regards,<br>
<br>
Mike GT<br>
</span><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:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Get
5GB of online storage for free! <a
href="http://clk.atdmt.com/UKM/go/msnnkmgl0010000005ukm/direct/01/">Get it Now!
</a></span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal><span class=ecxecxece><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
class=ecxecxece><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></span></div>
<p class=MsoNormal><span class=ecxecxece><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Get 5GB of online storage for free! <a
href="http://clk.atdmt.com/UKM/go/msnnkmgl0010000005ukm/direct/01/">Get it Now!
</a></span></span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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"'>Win
£3000 to spend on whatever you want at Uni! <a
href="http://clk.atdmt.com/UKM/go/101719803/direct/01/">Click here to WIN!</a> <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. 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"'>Use
Hotmail to send and receive mail from your different email accounts. <a
href="http://clk.atdmt.com/UKM/go/186394592/direct/01/">Find out how.</a> <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"'>View
your other email accounts from your Hotmail inbox. <a
href="http://clk.atdmt.com/UKM/go/186394592/direct/01/" target="_new">Add them
now.</a><o:p></o:p></span></p>
</div>
</body>
</html>