Version mismatch

[Morris, Eddie]

Hi Adam,
 
Take a look at note 1098805 section [5].
 
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.
 
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.
 
Regards,
Eddie

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Adam Kheil
Sent: 23 June 2009 15:23
To: Workflow group
Subject: Version mismatch


Hello Experts,
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 SWDSHEADER and  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?
 
Please advise.
 
 
Thanks
Adam


________________________________

Lauren found her dream laptop. Find the PC that's right for you.
<http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090623/1fbc3845/attachment.htm