Problems with transporting a workflow to another instance

[Dale Davis]

Hi Lindsey:
 
>From your memo, I am inferring that your workflow definition in SBX was=
 not
activated previously and that your (AC) role is based on a function mod=
ule?
If that is the case, was the function module transported  to SBX and ha=
s it
been generated?
I am not clear whether you changed the workflow to go to one user in SB=
X
by linking the step in the workflow definition to a userid or whether y=
ou
assigned the TS task to a user and left the link in the workflow defini=
tion
step blank.  If you did either,  you need to relink the step in the
workflow definition to the role and retransport the workflow definition=
 now
that you have validated that the role and the function module it refere=
nces
are there in SBX.
Also ensure that in SBX the agents linked to your TS task are possible
agents otherwise your role resolution will not work.
 
You might also want to run diagnostics against the workflow template us=
ing
tx: SWUD to ensure there are no additional hidden problems.
 
Regarding  your question on transport procedures:
 
For all new development we create workflow templates and standard tasks=
.
 
If there are PD org objects such as responsibilities, orgs  or position=
s, I
transport them and their relationships  before transporting the reposit=
ory
objects that reference them.
 
Next I batch workflows that consist of WS andTS tasks, and linked
respository objects such as roles, business object types, function modu=
les,
in the same workbench transport or set of workbench transports and
transport them after the org objects are imported successfully.
 
 
Note : For changes to existing WF tasks, I  transport the repository
objects such as business object types first, followed by the customizin=
g
objects such as WF and T tasks that reference them.
 
 
Regards,
Dale Davis Jones
IBM / SAP Certified
Senior SAP Workflow & PP Consultant - SAP Practice
 
IBM Global Services
Phone: 919-543-7678
               T/L 8-441-7678
  Internet Address: DKDAVIS at US.IBM.COM
 
.......You can never discover new oceans unless you have the courage to=
 
lose sight of the shore..........
 
 
Lindsey Stead <Lindsey.Stead at huskyenergy.ca>@MITVMA.MIT.EDU> on 02/11/2=
002
12:09:55 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Problems with transporting a workflow to another instance
 
 
 
 
Hi everyone...
 
I have created a small=A0workflow that sends a cash receipt  document f=
or
confirmation to the relevant users inbox. The workflow is triggered  by=
 FM
SWW_WI_START_SIMPLE and I use a role which calls a fn to work out which=
 
user gets the message. This works perfectly in DEV, however I cannot ge=
t it
to  work in SBX=A0 for testing. We are on 4.6B hotpackpack 10.=A0I have=
 
applied the OSS notes to handle any problems with versions of the workf=
low.
I  have looked at note 138411 that talks about the transport of PD obje=
cts
and and  I have used RHMOVE30 to create a transport for the PDWS( workf=
low)
&  PDTS(task) objects. I know it is the role that is the problem as I h=
ave
changed  the workflow to go to one user in SBX and it works. The role w=
as
transported to  SBX and is there - how do I transport the link to it? A=
lso
is there a certain  way we should transport non-sap delivered workflows=
?
 
Thanks to all..
=A0=A0 Lindsey Stead,
=A0=A0=A0Husky Energy
 
=