Workflow upgrades from 3.1H to 4.6X

[Roehlen, Peter]

Graeme,
 
Whilst we weren't using workflow extensively in before our upgrade to 4.6B
(we were on 3.0F), we did have 3 background customer tasks that were running
several thousand times a day using Network/PM Order status change as a
trigger.
 
Aside from having to update the BDC programming in the business object type
method (to cater for changed screen numbers), these customer tasks continue
to run flawlessly in our production system as customer tasks.  There was
zero effort required in workflow development to make these work in 4.6B even
though SAP have moved away from customer tasks to standard tasks.
 
Regards
 
Peter Roehlen
Team Lead - SAP Technical & Development
Powercor Australia Ltd
(03) 5430 4704 / 0409 950 263
 
 
 
-----Original Message-----
From: MacPherson, Graeme (AU - Melbourne) [mailto:gmacpherson at dc.com]
Sent: Thursday, 16 November 2000 11:50
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow upgrades from 3.1H to 4.6X
 
 
Hi Guys
 
Would anyone like to share their "war stories" on upgrading workflows from
31H to 4.6B/C. I have reviewed the OSS notes on this matter but would like
some input on strategy and possibly some lessons learned (do's and dont's)
which are not documented on the OSS. In particular, how is the continuity
ensured because I am assuming that there is very little one can do about the
active workflow instances created in 31H.
 
Do you have a cutover point when you switch off the 31H workflows and ask
users to action all outstanding work items before upgrade ?
 
Following this I presume you would have to take stock of all unactioned work
items and recreate the workflows after upgrade using a workflow start
transaction (presuming the volume was not too high).
 
Any comments would be appreciated.
 
Regards
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph: +613 9208 7100
Mob: 0414 473 554
**********************************************************************
Powercor Australia Ltd. This email and any file attachments are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in
error please tell us immediately by return email and delete the
document.
**********************************************************************