<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<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:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.7588a79e-a56e-4eb5-807e-a8a2451b6b86, li.7588a79e-a56e-4eb5-807e-a8a2451b6b86, div.7588a79e-a56e-4eb5-807e-a8a2451b6b86
{mso-style-name:7588a79e-a56e-4eb5-807e-a8a2451b6b86;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.c6d3c6c6-5c23-4132-8928-8063b150774c, li.c6d3c6c6-5c23-4132-8928-8063b150774c, div.c6d3c6c6-5c23-4132-8928-8063b150774c
{mso-style-name:c6d3c6c6-5c23-4132-8928-8063b150774c;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecgmailquote
{mso-style-name:ec_gmail_quote;}
span.ece
{mso-style-name:ec_e;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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 link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;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:10.0pt;font-family:Courier'>dynamic
parallel processing) </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Might
be of use to you too.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Best
Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Koenraad
Janssens<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Keneos
S.A.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Catherall, Andy<br>
<b>Sent:</b> 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='font-family:"Arial","sans-serif";color:blue'>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='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
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='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><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='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><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='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><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>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='font-family:"Arial","sans-serif";color:blue'>So,
my questions:</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>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='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 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='font-family:"Arial","sans-serif";color:blue'>Many
thanks for this information.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>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 align=center style='text-align:center'><span lang=EN-US>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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:12.0pt'>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 align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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 align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</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:12.0pt'><span class=ece><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><br>
<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><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Regards</span><br>
<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><br>
<i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Principal
Consultant</span></i><br>
<b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> </span></b><br>
<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><br>
<span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Amsterdamsestraatweg 40</span><br>
<span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>3743 DT Baarn</span><br>
<span lang=NL style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>The Netherlands</span><br>
<span lang=NL style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:navy'> </span><br>
<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><br>
<b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>F</span></b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'> +31 (0)88
40 40 499</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'><a
href="http://www.kirkmancompany.com/" target="_blank">www.kirkmancompany.com</a></span><br>
<span style='color:navy'> </span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:navy'> </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>------------------------------------------------------</span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>The
information contained in this message </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>may
be confidential and is intended to be </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>exclusively
for the addressee. Should you </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>receive
this message unintentionally, you are </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>kindly
requested not to make any use </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>whatsoever
of the contents. Please notify</span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>the
sender by return e-mail and delete </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:navy'>the
material from any computer.</span><br>
<span lang=NL style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:navy'>---------------------------------------------------- </span><br>
<span style='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'> </span><o:p></o:p></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><o:p></o:p></p>
</div>
<p class=MsoNormal> <o:p></o:p></p>
<p 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><o:p></o:p></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/"
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 align=center style='text-align:center'><span class=ece>
<hr size=2 width="100%" align=center>
</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:12.0pt'><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:12.0pt'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</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: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 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
style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:maroon'> to
learn more.</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:maroon'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span 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><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:10.0pt;font-family:"Verdana","sans-serif"'>-----------------------------------------</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:8.0pt;margin-right:0cm;margin-bottom:
8.0pt;margin-left:0cm'><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 </span><u><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'><a
href="mailto:mailerror@cadbury.com">mailerror@cadbury.com</a></span></u><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> and destroy all
copies.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:8.0pt;margin-right:0cm;margin-bottom:
8.0pt;margin-left:0cm'><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. </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>This
email originates from </span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Cadbury
Holdings Ltd </span><span style='font-size:10.0pt;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: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>
</span><o:p></o:p></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. </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Principal
trading address: </span><span style='font-size:10.0pt;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:10.0pt;font-family:"Verdana","sans-serif"'>-----------------------------------------</span><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>