<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5880" name=GENERATOR><!--[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-face {
font-family: Courier;
}
@font-face {
font-family: SimSun;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @SimSun;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt 72.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
P.7588a79e-a56e-4eb5-807e-a8a2451b6b86 {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: 7588a79e-a56e-4eb5-807e-a8a2451b6b86
}
LI.7588a79e-a56e-4eb5-807e-a8a2451b6b86 {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: 7588a79e-a56e-4eb5-807e-a8a2451b6b86
}
DIV.7588a79e-a56e-4eb5-807e-a8a2451b6b86 {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: 7588a79e-a56e-4eb5-807e-a8a2451b6b86
}
P.c6d3c6c6-5c23-4132-8928-8063b150774c {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: c6d3c6c6-5c23-4132-8928-8063b150774c
}
LI.c6d3c6c6-5c23-4132-8928-8063b150774c {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: c6d3c6c6-5c23-4132-8928-8063b150774c
}
DIV.c6d3c6c6-5c23-4132-8928-8063b150774c {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman","serif"; mso-style-name: c6d3c6c6-5c23-4132-8928-8063b150774c
}
SPAN.ecgmailquote {
mso-style-name: ec_gmail_quote
}
SPAN.ece {
mso-style-name: ec_e
}
SPAN.EmailStyle22 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: "Arial","sans-serif"; TEXT-DECORATION: none; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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-GB vLink=purple link=blue>
<DIV><SPAN class=908410814-09122009><FONT face=Arial color=#0000ff size=2>Thanks
for that, Koenraad. All warnings of dragons ahead gratefully
received!</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>JANSSENS
Koenraad<BR><B>Sent:</B> Wednesday 09 December 2009 13:18<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Workflow Upgrade issues (4.6c to
ECC 6)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Totally not on topic
but I recently ran into the issue corrected with note 1383979 which is also +-
an upgrade issue and will pop up when you create your first new wf with parallel
execution of subwf’s starting from a multiline container element. (</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Courier">dynamic parallel processing)
</SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Might be
of use to you too.</SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Best
Regards<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Koenraad
Janssens<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Keneos
S.A.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
lang=EN-US style="FONT-SIZE: 10pt; 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> Wednesday, December 09, 2009 1:56
PM<BR><B>To:</B> SAP Workflow Users' Group<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>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Hi
all</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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 subtleties behind it.
This thread seemed a very pertinent place to ask my
questions.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">However, there are hints
in this thread - and other similar ones - of people somehow managing
to cajole their workflow instances into continuing across the upgrade
boundary...</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">So, my
questions:</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Where are all the
fixes made such that 'old' versions of the workflows were still functional
even after the upgrade? Can they all be made in the 4.6c system, in advance of
the upgrade?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">How are all the fixes
made? If they cannot all be made in the 4.6c environment (e.g. the
corrected block-structure issue only manifests in ECC6), how are new versions
avoided?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Many thanks for this
information.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Andy</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN lang=EN-US>
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B><SPAN lang=EN-US
style="FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN lang=EN-US
style="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 lang=EN-US><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">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></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><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></P>
<DIV>
<P class=MsoNormal>Hi Mike,<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>A client of mine just went from 46B to ECC6, and we found the
following workflow problems:<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>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></P></DIV>
<DIV>
<P class=MsoNormal>2) Old FORMHTML.PROCESS steps short dumped, so we replaced
them with the shiny new form step.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>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></P></DIV>
<DIV>
<P class=MsoNormal>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></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>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></P></DIV>
<DIV>
<P class=MsoNormal><SPAN class=ecgmailquote>On 6/18/08, <B>Mike Gambier</B>
<<A href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</A>>
wrote:</SPAN> <o:p></o:p></P>
<DIV>
<P class=MsoNormal>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></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal>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></P>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN
class=ece><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Hi
Mike,</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Could
you elaborate on the painful stuff you were confronted by?</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Regards</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><o:p></o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Gijs
Houtzagers</SPAN><BR><I><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Principal
Consultant</SPAN></I><BR><B><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN></B><BR><B><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Kirkman</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> Company
B.V.</SPAN><BR><SPAN lang=NL
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Amsterdamsestraatweg
40</SPAN><BR><SPAN lang=NL
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">3743
DT Baarn</SPAN><BR><SPAN lang=NL
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">The
Netherlands</SPAN><BR><SPAN lang=NL
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Verdana','sans-serif'"> </SPAN><BR><B><SPAN
lang=NL
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">T</SPAN></B><SPAN
lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">
+31 (0)88 40 40 400</SPAN><BR><B><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">F</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> +31
(0)88 40 40 499</SPAN><BR><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"><A
href="http://www.kirkmancompany.com/"
target=_blank>www.kirkmancompany.com</A></SPAN><BR><SPAN
style="COLOR: navy"> </SPAN><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">------------------------------------------------------</SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">The
information contained in this message </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">may be
confidential and is intended to be </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">exclusively
for the addressee. Should you </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">receive
this message unintentionally, you are </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">kindly
requested not to make any use </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">whatsoever
of the contents. Please notify</SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">the
sender by return e-mail and delete </SPAN><BR><SPAN
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">the
material from any computer.</SPAN><BR><SPAN lang=NL
style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">----------------------------------------------------
</SPAN><BR><SPAN style="COLOR: navy"> </SPAN><o:p></o:p></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><o:p></o:p></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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><o:p></o:p></P></DIV>
<P class=MsoNormal> <o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt"><SPAN
style="FONT-SIZE: 10pt; 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><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Get 5GB of online
storage for free! <A
href="http://clk.atdmt.com/UKM/go/msnnkmgl0010000005ukm/direct/01/"
target=_blank>Get it Now! </A></SPAN><o:p></o:p></P></DIV></DIV>
<DIV>
<P class=MsoNormal><SPAN class=ece><o:p> </o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN class=ece>
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal><SPAN class=ece>Get 5GB of online storage for free! <A
href="http://clk.atdmt.com/UKM/go/msnnkmgl0010000005ukm/direct/01/"
target=_blank>Get it Now! </A></SPAN><o:p></o:p></P></DIV></DIV>
<P class=MsoNormal
style="MARGIN-BOTTOM: 12pt"><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"
target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><o:p></o:p></P></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><o:p> </o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<P class=MsoNormal>Win £3000 to spend on whatever you want at Uni! <A
href="http://clk.atdmt.com/UKM/go/101719803/direct/01/" target=_new>Click here
to WIN!</A> <o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Verdana','sans-serif'">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
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Verdana','sans-serif'"><A
title=http://www.cadbury.com/
href="http://www.cadbury.com/">www.cadbury.com</A></SPAN></U></B><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Verdana','sans-serif'"> to
learn more.</SPAN></B><o:p></o:p></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Verdana','sans-serif'"> </SPAN></B><o:p></o:p></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: 'Verdana','sans-serif'">Be
part of our "Purple Goes Green" commitments and don't print this
email.</SPAN></B><o:p></o:p></P>
<P class=c6d3c6c6-5c23-4132-8928-8063b150774c> <o:p></o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">-----------------------------------------</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"> </SPAN><o:p></o:p></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 8pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; mso-margin-top-alt: 8.0pt"><SPAN
style="FONT-SIZE: 10pt; 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 </SPAN><U><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Verdana','sans-serif'"><A
href="mailto:mailerror@cadbury.com">mailerror@cadbury.com</A></SPAN></U><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"> and destroy all
copies.</SPAN><o:p></o:p></P>
<P class=MsoNormal
style="MARGIN-BOTTOM: 8pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; mso-margin-top-alt: 8.0pt"><SPAN
style="FONT-SIZE: 10pt; 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.
</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">This email
originates from </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">Cadbury Holdings
Ltd </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">("Cadbury") or
Cadbury UK ("Cadbury UK") as the case may be.</SPAN><o:p></o:p></P>
<P class=MsoNormal> <o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; 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> </SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; 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. </SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">Principal trading
address: </SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">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><BR><BR></SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN lang=EN-US
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">-----------------------------------------</SPAN><o:p></o:p></P></DIV></DIV></DIV></BODY></HTML>