Version mismatch

[Mike Gambier]

Adam,

 

In our experience Workflow templates often fail to activate because one of the following has happened:

 

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.

 

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.

 

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.

 

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.

 

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.

 

All this assumes you are not transporting 'new' templates to back-dated test systems (where the target environment thinks it is in the past), as SAP doesn't support that.

 

Regards,
 

Mike GT


 


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.
_________________________________________________________________

MSN straight to your mobile - news, entertainment, videos and more.

http://clk.atdmt.com/UKM/go/147991039/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090623/0571312e/attachment.htm