<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1255">
<STYLE>.hmmessage P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>
<META content="MSHTML 6.00.2900.5880" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV><SPAN class=578445518-15012010><FONT face=Arial color=#0000ff>Thanks Mike
</FONT></SPAN></DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial color=#0000ff>[For a moment
there, I thought Jocelyn had answered my query too :-(
]</FONT></SPAN></DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial color=#0000ff>An update for
those searching in the future.</FONT></SPAN></DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial color=#0000ff>After a lot
more digging, I have found the following:</FONT></SPAN></DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=578445518-15012010></SPAN><FONT face=Arial><FONT
color=#0000ff>T<SPAN class=578445518-15012010>he warnings in the 'IMPORT' area
of the transport log are probably red herrings. I think SAP is handling the
different table sizes correctly and is just...um... <EM>warning</EM> me about
it.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=578445518-15012010>This
lead me to the view that my workflow data <EM>is</EM> in our ECC6 Dev
environment. The workflows have just not activated correctly/at
all...</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010>I then noticed that those workflows that have not
activated seemed to also be missing a couple of areas in the Transport Log. The
CHECK VERSION and METHODS entries were not there.
</SPAN></FONT></FONT><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010>Did this mean that the FM
rh_activate_wfobject_after_imp etc was not being
called?</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=578445518-15012010>I have
confirmed that the appropriate entries appear in SOBJ for PDWS objects, so I am
not sure why the AFTER IMPORT features do not appear to be running. <U>Anyone
got any ideas?</U> They are either running and failing silently (nothing in the
log or ST22), or they are not running at all. Yet the transport thinks it
was successful, except for this minor act of
activating.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=578445518-15012010>Back to
the workflows. I have further discovered that in SWDSHEADER, the 9999
versions of those failed workflows had exactly the change data I was
missing. So, how to run the 'activation' process, as if we'd just transported?
(SWUD and viewing the templates were insufficient, as they were only opening the
'old' version).</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010>I further discovered that the fantastic Mr Eddie
Morris had answered this question way back in early 2007 (<A
href="http://mailman.mit.edu/pipermail/sap-wug/2007-January/024840.html">http://mailman.mit.edu/pipermail/sap-wug/2007-January/024840.html</A>)</SPAN></FONT></FONT></DIV>
<DIV><SPAN class=578445518-15012010></SPAN><FONT face=Arial><FONT
color=#0000ff>T<SPAN class=578445518-15012010>his led me to OSS note 981295,
which in turn describes how to use program
RSWD_REPLICATE_FROM_9999.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=578445518-15012010>And so
now we appear to have active workflows at the correct versions! A little more
testing and analysis will be required to check that all associated objects &
linkages are peachy, but we're in a much better place than a few days
ago.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN class=578445518-15012010>So,
just the question regarding the AFTER IMPORT functionality
remaining.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><SPAN
class=578445518-15012010></SPAN></FONT></FONT> </DIV><FONT face=Arial><FONT
color=#0000ff><SPAN class=578445518-15012010></SPAN></FONT></FONT><FONT
face=Arial color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT><FONT
face=Arial color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT><FONT
face=Arial color=#0000ff></FONT>
<DIV><FONT face=Arial color=#0000ff></FONT><FONT face=Arial
color=#0000ff></FONT><BR><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff>Thanks wuggers!</FONT></SPAN></DIV>
<DIV><SPAN class=578445518-15012010><FONT face=Arial
color=#0000ff>Andy</FONT></SPAN></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<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 14 January 2010 13:25<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> RE: Transporting workflows from 4.6c to
ECC6?<BR></FONT><BR></DIV>
<DIV></DIV>Andy,<BR> <BR>The short answer is mostly 'yes',
but sometimes (typically where ECC 6 wants to deal with new tables)
also 'no'.<BR> <BR>The longer answer is probably more like
this:<BR> <BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">RE: ECC Upgrade - WF Transport
Issues?þ<BR>From: <A
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A> on behalf of
Keohan, Susan (<A href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</A>)
<BR>Sent: 06 November 2008 15:54:52 <BR>To: SAP Workflow Users' Group
(<A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>) <BR> 5
attachments | Download all attachments (115.9 KB) <BR> image001.jpg
(22.6 KB), image002.jpg (16.8 KB), image003.jpg (42.3 KB), image004.jpg (34.1
KB), ATT00001 (0.1 KB) <BR> <BR>Hi Mike, All potential
upgraders!<BR><BR>Well, I did find this helpful – <BR><A
href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1">https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1</A><BR> <BR>In
particular, there is one OSS Note (1068627) which is good because it lists a
lot of notes that may be helpful.<BR>We are on Basis Support Pack 15, so a lot
of them did not apply to us.<BR>I’ve filled out an OSS Message. SAP did
respond advising me to check: <BR>* 1175535 - Cross-release transport of
workflows<BR>If you look at section [5] of note 1098805 there are some
points<BR>I would like you to check. They are:<BR>Troubleshoot versions &
activation<BR>- Do the Source and Target systems have the same system date
&<BR>time?<BR>- If you created any new container elements in your workflow
can<BR>you make sure that the their data references also exist in the<BR>QA
system.<BR>- Did you create any new tasks and add them to the workflow
in<BR>the development system. If so please make sure that you
also<BR>transported the task to the quality system.<BR>- Have you checked
transaction SWDM -> Extras -> Transported<BR>workflows in the target
system? It will show up in red if<BR>there are any issues.<BR>* 1098805 -
Troubleshooting Tips & Tricks for workflow
issues<BR> <BR>Additionally, table SWDSHEADER, for version 9999 of the
workflow, should have the exact date and time stamp as the same entry in your
Dev Box.<BR>Many thanks to Eddie Morris for helping me get this
far.<BR> <BR>So far, no other resolution. I’ve deleted offending
container elements in Dev, re-added them, checked binding, re-transported, all
to no avail.<BR>I’ll keep you posted.<BR>Sue<BR>----<BR>Susan R. Keohan<BR>SAP
Workflow Specialist<BR>Enterprise Applications<BR>Information Services
Department<BR>MIT Lincoln Laboratory<BR>244 Wood Street, LI-200<BR>Lexington,
MA. 02420<BR>781-981-3561<BR><A
href="mailto:keohan@LL.MIT.EDU">keohan@LL.MIT.EDU</A><BR> <BR>--------------------------------------------------------------------------------<BR>From:
<A href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A>
[mailto:sap-wug-bounces@mit.edu] On Behalf Of Mike Gambier<BR>Sent: Wednesday,
November 05, 2008 12:27 PM<BR>To: <A
href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A><BR>Subject: RE: ECC Upgrade
- WF Transport Issues?<BR> <BR>Hi Sue,<BR> <BR>We're at the tail-end
of a long protracted code merge between 4.6c and ECC 6 and our experiences of
the whole WF Transport area are these:<BR><BR>1. SAP categorically does NOT
support transporting 4.6c changes to ECC 6 definitions. And from what we've
been told they never will either, despite our complaints that they need to
consider they're existing customers who can't just upgrade
overnight.<BR> <BR>2. SAP expects clients to upgrade their definitions
once and once only. And therefore their migration tools and programs are
written to update the new tables from the 'old' tables once and once
only.<BR> <BR>3. Basically speaking you have to assume that most changes
to containers and container elements will NOT be Transportable and will have
to be manually applied directly in ECC 6. Thankfully, binding changes seem to
be unaffected for the most part although there too some things have crept in
that might catch you because of unicode parsing (there's new syntax added by
SWDD for type definitions that you can't add in 4.6c).<BR> <BR>4. Some
brand new WF Definition features have to be defaulted but these values may not
be ideal for you. For instance we have chosen to stick to the 'old' STRUCTURE
PERSISTENCE conatiner tables (SWW_CONTOB) but we need to explicitly state this
in the WF Definition header settings otherwise furture versions may decide to
switch to the new tables (Compatiblity setting). And we've found that on
occasion 4.6c Transports have a nasty habit of re-initialising some of these
defaults...<BR> <BR>5. Dummy nodes in ECC 6 cause havoc until a Block
Correction is carried out, as you have found out. These go away but come back
if you re-import from 4.6c of course. Nice! The fault is deep down in the new
logic for determining step types and the fact that ECC 6 adds an extra piece
of data somewhere to define a dummy block that you can't
transport.<BR> <BR>6. Multi-line tables now have to be handled with a
brand new container element that 4.6c can't deal with. That was a fun one to
work out. You actually have to hack your binding in text editor mode to insert
the new syntax if you want to pacth this kind of thing up
(WFParForEach).<BR> <BR>The Transport mechanism in 4.6c can only succeed
in delivering changes where the tables in ECC 6 have remained in place and are
still in use. Thankfully this means that in most cases the changes to actual
step logic and binding does make it through, but be careful where the new
logic being added is based on new container elements (see 3). <BR> <BR>To
be fair I appreciate SAP's dilemma a bit because the jump from 4.6c to ECC 6
in terms of Workflow is subtle but huge. The addition of XI/PI/BPM (whatever
they call it now) and the whole revamp of the Workflow engine in ABAP Classes
has meant a complete rethink in a lot of key areas. <BR> <BR>But I think
clients are currently faced with a painful choice at the moment which leaves a
sour taste in my mouth to be honest. They either send Transports through and
patch things up manually (as we have had to do) or they carry out parallel
changes and keep their development codestreams apart (at the risk of missing
stu! ff). Either way the upgrade becomes quite a pain if you use Workflow a
lot.<BR> <BR>By the way, be aware that the tables for Event Linkages have
also changed, so SWETYPV is based on a completely different table view and
hence Transports from 4.6c are utterly useless.<BR> <BR></BLOCKQUOTE>
<P dir=ltr><BR>Regards,<BR> <BR>Mike GT<BR> </P>
<HR id=stopSpelling>
Subject: Transporting workflows from 4.6c to ECC6?<BR>Date: Thu, 14 Jan 2010
06:03:44 -0700<BR>From: andy.m.catherall@cadbury.com<BR>To:
sap-wug@mit.edu<BR><BR>
<STYLE>.ExternalClass P.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass LI.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass DIV.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass TABLE.ecxa4cf2f35-85f1-416d-928f-c600a8d649f9Table {
MARGIN-BOTTOM: 0pt
}
.ExternalClass DIV.ecxSection1 {
page: Section1
}
</STYLE>
<STYLE>.ExternalClass P.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass LI.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass DIV.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4 {
MARGIN-BOTTOM: 0pt
}
.ExternalClass TABLE.ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4Table {
MARGIN-BOTTOM: 0pt
}
.ExternalClass DIV.ecxSection1 {
page: Section1
}
</STYLE>
<P class=ecxa4cf2f35-85f1-416d-928f-c600a8d649f9>
<P class=ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>Hi</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>Is it possible to
[successfully] transport 4.6c workflow developments (esp. WS objects) to ECC6?
</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>We still have our 4.6c
path-to-production, and we have our parallel ECC6 project landscape for the
upgrade. Some urgent changes/fixes have been made to a few of our production
workflows, and these transports have been cloned back into our ECC6 Dev &
Sandbox systems.</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>That has not gone
well... :o(</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>We have noticed two
key features:</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>1) In most cases, the
WS objects are not activating. There is no error, nor any clear warning
explaining why not.</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>2) In most cases, we
have seen warnings along the following lines:</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>
different nametabs for table HRS1212</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>
different nametabs for table SWBRULECOU<BR>
etc.</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>Clearly, the 'new'
tables are of a different size to the 4.6c tables, hence the offsets are
incorrect. </SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>However, in at least
one example - involving two WS templates - the activations <EM>did</EM>
occur despite the warnings.</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>So,
i</SPAN></FONT><FONT face=Verdana><SPAN class=ecx552134512-14012010>s there
evidence/experience of successful transports of this nature out there, and I
just need to find the appropriate correction or fix? Or, is this approach
impossible?</SPAN></FONT></DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN
class=ecx552134512-14012010></SPAN></FONT> </DIV>
<DIV><FONT face=Verdana><SPAN class=ecx552134512-14012010>I further note that we
are only on SAPKB70103 - 4,5 & 6 exist, so I am working my way through these
notes to see if there are any solutions. For example, note 1276795 may
help, though it does not sound ideal. </DIV>
<DIV><BR></DIV></SPAN></FONT>
<DIV><SPAN class=ecx552134512-14012010><FONT face=Verdana>Thanks again,
guys!</FONT></SPAN></DIV>
<P dir=ltr align=left><FONT face=HouschkaBold color=#0000ff>Andy
Catherall</FONT> <BR><FONT face=HouschkaBold color=#0000ff>Technical Analyst -
SAP Workflow, IXOS & DMS</FONT> </P><FONT face=HouschkaBold size=1><IMG
height=32 src="cid:578445518@15012010-2A62" width=80 border=0></FONT><BR><FONT
face=HouschkaBold size=1>Int: 751 0556</FONT> <BR><FONT face=HouschkaBold
size=1>Ext: +44 (0)121 486 0556</FONT> <BR><FONT face=HouschkaBold
size=1>Mobile: +44 (0)7813 025481</FONT> <BR>
<DIV> </DIV><BR>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN> </P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><B><SPAN lang=EN-GB
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 lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Verdana','sans-serif'"><A
title=http://www.cadbury.com/ href="http://www.cadbury.com/"><SPAN
style="COLOR: blue">www.cadbury.com</SPAN></A></SPAN></U></B><B><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Verdana','sans-serif'"> to
learn more.</SPAN></B><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><B><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; COLOR: maroon; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN></B> </P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><B><SPAN lang=EN-GB
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></P>
<P class=ecxdd320c0b-5eb7-4b98-b7d7-a17a3ae451b4> </P><BR>
<DIV><SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><FONT
face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">-----------------------------------------</SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN> </P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN> </P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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:</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></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><SPAN> </SPAN></SPAN><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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. each of which is registered in England and Wales. </SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><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></SPAN><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></SPAN></P>
<P class=ecxMsoNormal style="LINE-HEIGHT: normal"><SPAN
style="FONT-SIZE: 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Verdana','sans-serif'">-----------------------------------------</SPAN></P></SPAN></SPAN></FONT></SPAN></SPAN><BR></DIV><BR>
<HR>
Got a cool Hotmail story? <A
href="http://clk.atdmt.com/UKM/go/195013117/direct/01/" target=_new>Tell us
now</A> </BODY></HTML>