<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Adam,<BR>
<BR>
In our experience Workflow templates often fail to activate because one of the following has happened:<BR>
<BR>
1. Changes made to the WF definition are relying on other objects to be adjusted (e.g. DDIC structure changes) and these may not have gone across or become properly active. Sometimes a simple syntax check can flush these out, no doubt you've checked though.<BR>
<BR>
2. Agent Assignments for new dialog tasks fail to active properly (sometimes the General Flag setting doesn't come across). This often appears in a check in SWDD on the template itself and sometimes can be corrected in the target system by clicking on the General Task pop-up option.<BR>
<BR>
3. General issues with the runtime environment on the target system where some objects need to be generated first - often affects first time use. This one's a bit harder to diagnose. The best bet here is to force your BOR objects, if you are using any, to re-generate (we do that via a program) drop the buffers (SWU_OBUF) and try another import.<BR>
<BR>
Susan quite rightly points out that version numbering cannot be trusted between systems, although in ECC 6 you do have the 'original version' from the DEV system being dragged across these days which is handy.<BR>
<BR>
Sometimes just by displaying the definition in the target environment or using the SWUD test features you can trigger the target system to accept the new version once you've checked out these 3 areas.<BR>
<BR>
All this assumes you are <STRONG>not </STRONG>transporting 'new' templates to back-dated test systems (where the target environment thinks it is in the past), as SAP doesn't support that.<BR>
<BR>
Regards,<BR> <BR>
Mike GT<BR>
<BR> <BR>
<HR id=stopSpelling>
From: keohan@ll.mit.edu<BR>To: sap-wug@mit.edu<BR>Date: Tue, 23 Jun 2009 10:53:23 -0400<BR>Subject: RE: Version mismatch<BR><BR>
<STYLE>
.ExternalClass .EC_shape
{;}
</STYLE>
<STYLE>
</STYLE>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:blue;text-decoration:underline;}
.ExternalClass p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:'Times New Roman';}
.ExternalClass span.EC_EmailStyle19
{font-family:'Times New Roman';color:black;font-weight:normal;font-style:normal;text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">Hi Adam,</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">First of all, the new version of the workflow template that went to QA – were you looking at it immediately after the transport was applied? The new version should be activated at midnight (Cinderella Effect) or you must manually activate it.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">I wouldn’t worry about the version numbers – and I certainly wouldn’t mess with the tables you mentioned. What is important is that in the header (under the ‘hat’ in the WF Builder) you see that the change date reflects what you would expect. </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black">Mike Pokraka once said: </SPAN></FONT><FONT size=2><SPAN style="FONT-SIZE: 11pt"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">Systems generate their own versions independently of one another - outside of DEV this happens automatically at transport.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt">So you can generate 20 versions in DEV, transport your final one to QA and it will become version 0001 - it is still only the second version in the QA system. Conversely you can retransport one DEV version and have a higher QA version. Nothing wrong with that either.</SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=2><SPAN style="FONT-SIZE: 11pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 11pt; COLOR: black"> </SPAN></FONT></P>
<DIV>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">----</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Susan R. Keohan</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">SAP Workflow Specialist</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Enterprise</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black"> Applications</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Information Services Department</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">MIT Lincoln Laboratory</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">244 Wood Street</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">, LI-200</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">Lexington</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">, MA</SPAN></FONT><FONT color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">. 02420</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">781-981-3561</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=2><SPAN style="FONT-SIZE: 10pt; COLOR: black">keohan@LL.MIT.EDU</SPAN></FONT><FONT color=black><SPAN style="COLOR: black"></SPAN></FONT></P>
<P class=EC_MsoNormal><FONT face="Times New Roman" color=black size=3><SPAN style="FONT-SIZE: 12pt; COLOR: black"> </SPAN></FONT></P></DIV>
<DIV>
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=EC_MsoNormal><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"> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Adam Kheil<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, June 23, 2009 10:23 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Workflow group<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Version mismatch</SPAN></FONT></P></DIV>
<P class=EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </SPAN></FONT></P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">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><I><FONT face=Verdana><SPAN style="FONT-FAMILY: Verdana">SWDSHEADER and </SPAN></FONT></I></EM><I><SPAN style="FONT-STYLE: italic"> 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?</SPAN></I><BR> <BR><EM><I><FONT face=Verdana><SPAN style="FONT-FAMILY: Verdana">Please advise.</SPAN></FONT></I></EM><BR> <BR> <BR><EM><I><FONT face=Verdana><SPAN style="FONT-FAMILY: Verdana">Thanks</SPAN></FONT></I></EM><BR><EM><I><FONT face=Verdana><SPAN style="FONT-FAMILY: Verdana">Adam</SPAN></FONT></I></EM></SPAN></FONT></P>
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><FONT face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=EC_MsoNormal><FONT face=Verdana size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Lauren found her dream laptop. <A href="http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290">Find the PC that’s right for you.</A></SPAN></FONT></P></DIV><br /><hr />View your Twitter and Flickr updates from one place – <a href='http://clk.atdmt.com/UKM/go/137984870/direct/01/' target='_new'>Learn more!</a></body>
</html>