<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.3105.105" name=GENERATOR></HEAD>
<BODY style="FONT: 8pt MS Sans Serif; MARGIN-LEFT: 2px; MARGIN-TOP: 2px">
<DIV><FONT size=1>Thanks for the reply. </FONT></DIV>
<DIV><FONT size=1>Initially I transported the workflow with workflow step linked
to a role, this would not activate (the task I have set up as a general
task). Then I linked the step to a user id to check the workflow itself was OK
and transported it -this works. To make a long story short I now have two
copies of this workflow in SBX - one with the step linked to a userid(working)
and one linked to a role (not working). This one will not activate due to the
error WD:451 Role '91000001' is not available . I have displayed the role in SBX
and the fn associated with it is activated. I guess the next thing I will
</FONT></DIV>
<DIV> </DIV>
<DIV>>>> dkdavis@us.ibm.com 02/11/02 12:12PM >>><BR>Hi
Lindsey:<BR><BR>From your memo, I am inferring that your workflow definition in
SBX was not<BR>activated previously and that your (AC) role is based on a
function module?<BR>If that is the case, was the function module
transported to SBX and has it<BR>been generated?<BR>I am not clear whether
you changed the workflow to go to one user in SBX<BR>by linking the step in the
workflow definition to a userid or whether you<BR>assigned the TS task to a user
and left the link in the workflow definition<BR>step blank. If you did
either, you need to relink the step in the<BR>workflow definition to the
role and retransport the workflow definition now<BR>that you have validated that
the role and the function module it references<BR>are there in SBX.<BR>Also
ensure that in SBX the agents linked to your TS task are possible<BR>agents
otherwise your role resolution will not work.<BR><BR>You might also want to run
diagnostics against the workflow template using<BR>tx: SWUD to ensure there are
no additional hidden problems.<BR><BR>Regarding your question on transport
procedures:<BR><BR>For all new development we create workflow templates and
standard tasks.<BR><BR>If there are PD org objects such as responsibilities,
orgs or positions, I<BR>transport them and their relationships
before transporting the repository<BR>objects that reference them.<BR><BR>Next I
batch workflows that consist of WS andTS tasks, and linked<BR>respository
objects such as roles, business object types, function modules,<BR>in the same
workbench transport or set of workbench transports and<BR>transport them after
the org objects are imported successfully.<BR><BR><BR>Note : For changes to
existing WF tasks, I transport the repository<BR>objects such as business
object types first, followed by the customizing<BR>objects such as WF and T
tasks that reference them.<BR><BR><BR>Regards,<BR>Dale Davis Jones<BR>IBM / SAP
Certified<BR>Senior SAP Workflow & PP Consultant - SAP Practice<BR><BR>IBM
Global Services<BR>Phone:
919-543-7678<BR>
T/L 8-441-7678<BR> Internet Address: DKDAVIS@US.IBM.COM<BR><BR>.......You
can never discover new oceans unless you have the courage to<BR>lose sight of
the shore..........<BR><BR><BR>Lindsey Stead
<Lindsey.Stead@huskyenergy.ca>@MITVMA.MIT.EDU> on
02/11/2002<BR>12:09:55 PM<BR><BR>Please respond to "SAP Workflow Users' Group"
<SAP-WUG@MITVMA.MIT.EDU><BR><BR>Sent by: SAP Workflow
<Owner-SAP-WUG@MITVMA.MIT.EDU><BR><BR><BR>To:
SAP-WUG@MITVMA.MIT.EDU<BR>cc:<BR>Subject: Problems with
transporting a workflow to another instance<BR><BR><BR><BR><BR>Hi
everyone...<BR><BR>I have created a small workflow that sends a cash
receipt document for<BR>confirmation to the relevant users inbox. The
workflow is triggered by FM<BR>SWW_WI_START_SIMPLE and I use a role which
calls a fn to work out which<BR>user gets the message. This works perfectly in
DEV, however I cannot get it<BR>to work in SBX for testing. We are
on 4.6B hotpackpack 10. I have<BR>applied the OSS notes to handle any
problems with versions of the workflow.<BR>I have looked at note 138411
that talks about the transport of PD objects<BR>and and I have used
RHMOVE30 to create a transport for the PDWS( workflow)<BR>& PDTS(task)
objects. I know it is the role that is the problem as I have<BR>changed
the workflow to go to one user in SBX and it works. The role was<BR>transported
to SBX and is there - how do I transport the link to it? Also<BR>is there
a certain way we should transport non-sap delivered
workflows?<BR><BR>Thanks to all..<BR> Lindsey
Stead,<BR> Husky Energy<BR><BR></DIV></BODY></HTML>