Version mismatch

Sue Doughty Sue.Doughty at odfl.com
Tue Jun 23 11:39:08 EDT 2009


Adam,

 

Did you do a syntax check in the QA system from the workflow builder?
That will probably tell you why it did not activate.

 

Regards,

Sue T. Doughty

SAP Workflow Specialist

Old Dominion Freight Line, Inc.

500 Old Dominion Way

Thomasville, NC 27360

Phone:  (336) 822-5189

Toll Free (800 ) 432-6335, ext. 5189

Email:  sue.doughty at odfl.com

________________________________

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

 

Thanks Susan and Eddie for a quick reply. I made a transport yesterday
and checked this morning to see if it is because of the Cinderella
Effect, but in QA when I went to SWDD Status box says "Runtime Exists,
Saved". Eddie, I did add some new container elements and those are not
based on the  custom table. Susan please let me know how do I manually
activate the latest version in QA? 
 
Thanks
Adam
 

________________________________

From: keohan at ll.mit.edu
To: sap-wug at mit.edu
Date: Tue, 23 Jun 2009 10:53:23 -0400
Subject: RE: Version mismatch

Hi Adam,

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.

 

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.  

 

Mike Pokraka once said: 

Systems generate their own versions independently of one another -
outside of DEV this happens automatically at transport.

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.

 

 

----

Susan R. Keohan

SAP Workflow Specialist

Enterprise Applications

Information Services Department

MIT Lincoln Laboratory

244 Wood Street, LI-200

Lexington, MA. 02420

781-981-3561

keohan at LL.MIT.EDU

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Adam Kheil
Sent: Tuesday, June 23, 2009 10:23 AM
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> 

 

________________________________

Hotmail(r) has ever-growing storage! Don't worry about storage limits.
Check it out.
<http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tu
torial_Storage_062009> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090623/22f2f060/attachment.htm


More information about the SAP-WUG mailing list