<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><head><META content="text/html; charset=utf-8" http-equiv="Content-Type">
<STYLE><!-- /* Style Definitions */ p.7588a79e-a56e-4eb5-807e-a8a2451b6b86, li.7588a79e-a56e-4eb5-807e-a8a2451b6b86, div.7588a79e-a56e-4eb5-807e-a8a2451b6b86, table.7588a79e-a56e-4eb5-807e-a8a2451b6b86Table {margin:0cm; margin-bottom:.0001pt;}div.Section1 {page:Section1;}--></STYLE>
<META content="text/html; charset=utf-8" http-equiv="Content-Type">
<STYLE><!-- /* Style Definitions */ p.c6d3c6c6-5c23-4132-8928-8063b150774c, li.c6d3c6c6-5c23-4132-8928-8063b150774c, div.c6d3c6c6-5c23-4132-8928-8063b150774c, table.c6d3c6c6-5c23-4132-8928-8063b150774cTable {margin:0cm; margin-bottom:.0001pt;}div.Section1 {page:Section1;}--></STYLE>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Tahoma
}
</STYLE>
<META content="MSHTML 6.00.2900.5880" name=GENERATOR></head><BODY>
<P CLASS="7588a79e-a56e-4eb5-807e-a8a2451b6b86">
<P CLASS="c6d3c6c6-5c23-4132-8928-8063b150774c">
<DIV><SPAN class=156511519-08122009><FONT color=#0000ff face=Arial>Hi
all</FONT></SPAN></DIV>
<DIV><SPAN class=156511519-08122009><FONT color=#0000ff face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=156511519-08122009><FONT color=#0000ff face=Arial>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 class=562264707-09122009>ties</SPAN> behind it. This thread seemed a very
pertinent place to ask my question<SPAN class=562264707-09122009>s</SPAN>.</FONT></SPAN></DIV>
<DIV><SPAN class=156511519-08122009><FONT color=#0000ff face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=156511519-08122009></SPAN><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>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></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>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></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>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></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>However,
there are hints in th<SPAN class=968284307-09122009>is thread - and other
similar</SPAN> <SPAN class=968284307-09122009>ones - </SPAN>of people
somehow managing to cajole their workflow instances into continuing across the
upgrade boundary...</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>So, my
question<SPAN class=968284307-09122009>s</SPAN>:</SPAN></FONT></DIV>
<DIV><SPAN class=156511519-08122009><FONT face=Arial><FONT color=#0000ff>Where <SPAN class=968284307-09122009>are </SPAN>all the fixes
made such that 'old' versions of the workflows were still functional even
after the upgrade?<SPAN class=968284307-09122009> Can they all be made in the
4.6c system, in advance of the upgrade?</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=156511519-08122009><FONT color=#0000ff face=Arial><SPAN class=968284307-09122009>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 class=562264707-09122009> only manifests in ECC6</SPAN>), how are new versions
avoided?</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=156511519-08122009><FONT face=Arial><FONT color=#0000ff><SPAN class=968284307-09122009></SPAN></FONT></FONT></SPAN> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>Many thanks
for this information.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial><SPAN class=156511519-08122009>Andy</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial></FONT> </DIV><BR>
<DIV align=left class=OutlookMessageHeader dir=ltr lang=en-us>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> 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)<BR></FONT><BR></DIV>
<DIV></DIV>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 <BR><BR>
<HR>
<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><BR>
<DIV>Hi Mike,</DIV>
<DIV> </DIV>
<DIV>A client of mine just went from 46B to ECC6, and we found the following
workflow problems:</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV>2) Old FORMHTML.PROCESS steps short dumped, so we replaced them with the
shiny new form step.</DIV>
<DIV>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.</DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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> </DIV>
<DIV><SPAN class=EC_gmail_quote>On 6/18/08, <B class=EC_gmail_sendername>Mike
Gambier</B> <<A href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex; BORDER-LEFT: #ccc 1px solid">
<DIV>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<BR>
<BLOCKQUOTE>
<HR>
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
<DIV><SPAN class=EC_e id=EC_q_11a9ac9a377cf684_1><BR><BR>
<DIV><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi
Mike,</SPAN></FONT><BR><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Could you elaborate
on the painful stuff you were confronted by?</SPAN></FONT><BR><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Regards</SPAN></FONT><BR><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> </SPAN></FONT><BR>
<DIV><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Gijs
Houtzagers</SPAN></FONT><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT><BR><I><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-STYLE: italic; FONT-FAMILY: Arial">Principal
Consultant</SPAN></FONT></I><BR><B><FONT color=navy face=Arial><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> </SPAN></FONT></B><BR><B><FONT color=navy face=Arial><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Kirkman</SPAN></FONT></B><FONT color=navy face=Arial><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> Company
B.V.</SPAN></FONT><FONT color=navy face=Verdana><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Amsterdamsestraatweg
40</SPAN></FONT><FONT color=navy face=Verdana><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">3743 DT
Baarn</SPAN></FONT><FONT color=navy face=Verdana><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The
Netherlands</SPAN></FONT><FONT color=navy face=Verdana><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Verdana><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"> </SPAN></FONT><BR><B><FONT color=navy face=Arial><SPAN lang=NL style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">T</SPAN></FONT></B><FONT color=navy face=Arial><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> +31 (0)88 40 40
400</SPAN></FONT><FONT color=navy face=Verdana><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><B><FONT color=navy face=Arial><SPAN lang=EN-GB style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">F</SPAN></FONT></B><FONT color=navy face=Arial><SPAN lang=EN-GB style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> +31 (0)88 40 40
499</SPAN></FONT><FONT color=navy face=Verdana><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial><SPAN lang=EN-GB style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><A href="http://www.kirkmancompany.com/" target=_blank>www.kirkmancompany.com</A></SPAN></FONT><FONT color=navy><SPAN style="COLOR: navy"></SPAN></FONT><BR><FONT color=navy face="Times New Roman" size=3><SPAN lang=EN-GB style="FONT-SIZE: 12pt; COLOR: navy"> </SPAN></FONT><FONT color=navy face=Arial size=2><SPAN lang=EN-GB style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">------------------------------------------------------</SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">The information
contained in this message </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">may be confidential
and is intended to be </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">exclusively for the
addressee. Should you </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">receive this message
unintentionally, you are </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">kindly requested not
to make any use </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">whatsoever of the
contents. Please notify</SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">the sender by return
e-mail and delete </SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=EN-GB style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">the material from
any computer.</SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face=Arial size=1><SPAN lang=NL style="FONT-SIZE: 8pt; COLOR: navy; FONT-FAMILY: Arial">----------------------------------------------------
</SPAN></FONT><FONT color=navy face=Verdana size=2><SPAN lang=NL style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Verdana"></SPAN></FONT><BR><FONT color=navy face="Times New Roman" size=3><SPAN lang=EN-GB style="FONT-SIZE: 12pt; COLOR: navy"> </SPAN></FONT><BR></DIV><FONT color=navy face=Arial size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> </SPAN></FONT><BR>
<DIV>
<DIV align=center style="TEXT-ALIGN: center"><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center SIZE=2 width="100%">
</SPAN></FONT></DIV><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> <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><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Mike Gambier<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> dinsdag 17 juni 2008
17:12<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> SAP Workflow
Users' Group<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B>
Workflow Upgrade issues (4.6c to ECC 6)</SPAN></FONT><BR></DIV><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT><BR>
<P style="MARGIN-BOTTOM: 12pt"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">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></FONT></P>
<DIV align=center style="TEXT-ALIGN: center"><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
<HR align=center SIZE=2 width="100%">
</SPAN></FONT></DIV><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">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></FONT><BR></DIV></SPAN></DIV></BLOCKQUOTE>
<DIV><SPAN class=EC_e id=EC_q_11a9ac9a377cf684_3><BR>
<HR>
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></DIV></DIV><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><BR><BR></BLOCKQUOTE></DIV><BR><BR>
<HR>
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> </P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"> </SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><B><SPAN LANG="EN-GB" STYLE="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: maroon; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB">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-FAMILY: 'Verdana','sans-serif'; COLOR: blue; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB"><A HREF="http://www.cadbury.com/" TITLE="http://www.cadbury.com/"><SPAN STYLE="COLOR: blue; mso-bidi-font-size: 11.0pt">www.cadbury.com</SPAN></A></SPAN></U></B><B><SPAN LANG="EN-GB" STYLE="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: maroon; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB"> to learn more.</SPAN></B><SPAN LANG="EN-GB" STYLE="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><B><SPAN LANG="EN-GB" STYLE="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: maroon; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB"> </SPAN></B></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><B><SPAN LANG="EN-GB" STYLE="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: green; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-GB">Be part of our "Purple Goes Green" commitments and don't print this email.</SPAN></B></P>
<P CLASS="c6d3c6c6-5c23-4132-8928-8063b150774c"> </P></P>
<DIV><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"><FONT FACE="Verdana" SIZE="2"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'">
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'">-----------------------------------------</SPAN><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'"> </SPAN><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 8pt 0in"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: SimSun">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-FAMILY: 'Verdana','sans-serif'; COLOR: blue; FONT-SIZE: 10pt; mso-fareast-font-family: SimSun; mso-bidi-font-size: 11.0pt"><A HREF="mailto:mailerror@cadbury.com">mailerror@cadbury.com</A></SPAN></U><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: SimSun"> and destroy all copies.</SPAN><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 8pt 0in"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: SimSun">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><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: SimSun">This email originates from </SPAN><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'">Cadbury Holdings Ltd </SPAN><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial">("Cadbury") or Cadbury UK ("Cadbury UK") as the case may be.</SPAN><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"> </SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'">Cadbury Holdings Ltd: registered in England and Wales, registered no. 52457<BR>Registered office address:</SPAN><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt"> 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><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'"><SPAN STYLE="mso-spacerun: yes"> </SPAN></SPAN><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial">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><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Verdana; mso-fareast-language: EN-GB">Principal trading address: </SPAN><SPAN STYLE="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt">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 STYLE="mso-special-character: line-break"><BR STYLE="mso-special-character: line-break"></SPAN><SPAN STYLE="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'"></SPAN></P>
<P CLASS="MsoNormal" STYLE="LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"><SPAN STYLE="LINE-HEIGHT: 115%; FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">-----------------------------------------</SPAN></P></SPAN></SPAN></FONT></SPAN></SPAN>
<P></P></DIV></BODY></HTML>