<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<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.3527" name=GENERATOR></HEAD>
<BODY class=hmmessage>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>Hi Adam,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>Take a look at note 1098805 section [5].</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>If the transported template does not activate automatically then
it usually means that the change made is not compatible with the target system.
E.g. did you add a new container element or task. If the new container is based
on a custom table reference then make sure the table exists in the target
system.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>If you have created a new task in the source system make sure the
task is transported to the target system. Makre sure any newly created objects
are transport to the target system too....not only the workflow
template.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=049015014-23062009><FONT face=Arial
color=#0000ff>Eddie</FONT></SPAN></DIV><BR>
<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>Adam Kheil<BR><B>Sent:</B>
23 June 2009 15:23<BR><B>To:</B> Workflow group<BR><B>Subject:</B> Version
mismatch<BR></FONT><BR></DIV>
<DIV></DIV>Hello Experts,<BR>We have a version mismatch in DEV, QA and
production. We made some cjanges to the workflow template and transported it to
QA but in the QA the latest version transported did not get activated
autonmatically. I did search for this issue and found one posting
suggesting to compare versions in tables <EM>SWDSHEADER and </EM><I>
HRS1205. Versions in these two tables do not match. How do I correct this in QA
and production (after I transport it)? Do i have to manually update table
HRS1205 with the latest version?</I><BR><EM></EM> <BR><EM>Please
advise.</EM><BR><EM></EM> <BR><EM></EM> <BR><EM>Thanks</EM><BR><EM>Adam</EM><BR><BR>
<HR>
Lauren found her dream laptop. <A
href="http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290"
target=_new>Find the PC that’s right for you.</A> </BODY></HTML>