Workflow differences 3.1I to 4.6C

[Becker Stephan (extern)]

Roger,
 
you should always only use the supertype in workflows. That's what
delegation is for; have a look at the delegation section of the online
documentation, this explains why and how delegation works. One of the big
advantages of delegation is that you have access to child object components
from the parent. One of the main disadvantages of using child types is that
a lot of standard pieces of SAP functionality cease to function properly, as
you found out. One example that I found in a workflow I just inherited is
that the link to the workflow log from accounting documents didn't work
because the custom workflow didn't use the standard objects..
Delegation is available since 3.0.
 
In general terms, workflow tends to be stable during upgrades. A big caveat
is of course custom-developed functionality, the stability of which tends to
stand and fall with the proximity to SAP standard code, i.e. usage of SAP
standard function modules wherever possible, and other good coding
standards.
 
Apart from that, there are one or two good OSS notes about that topic (e.g.
152871 Release Upgrade considerations for workflow, thanks to Alan's useful
list on www.workfowing.com).
 
I hope this helps,
Stephan
 
 
 
 
 
-----Original Message-----
From: Roger Myers [mailto:rmyers at hciww.com]
Sent: Friday, November 23, 2001 4:18 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow differences 3.1I to 4.6C
 
 
We've just upgraded to 4.6C from 3.1I.
 
We have been using workflow for a number of years in 3.1I. Two of our
productive workflows utilize object subtypes. One is a subtype of BUS2032
the other is a subtype of VBRK.
 
Following the upgrade, the workflows based on the subtype of BUS2032
continued to work with no modification. The workflow based on the subtype of
VBRK failed. Each workflow specifically referenced the subtype object
(object & method) in the workflow tasks and as triggering events.
 
After a number of tries I managed to get the VBRK workflow functioning by
referencing the parent object in the workflow tasks and as the triggering
event. To my surprise, the sub object's events were available to the parent.
I suspect none of this is news to any of you on 4.6C.
 
My purpose here is to discover if there any other land mines that I need to
look out for.
 
All responses are truly appreciated.
 
R Myers
Brenntag Canada
416-503-6873
 
 
This email and any files transmitted with it 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 notify
the hciww.com system manager by forwarding this email to
postmaster at hciww.com
 
This footnote also confirms that this email message has been swept by
Norton AntiVirus for Internet Email Gateway for the presence of
computer viruses.