Role Error in Workflow

[Louise Morgan]

Thanks for the suggestion Stephen but there isn't anything in the =
branch
following the administrator user decision (if a positive decision is =
made,
which it has been) and the approval step.  The administrator check is =
just a
standard user decision, and the variables passed into the subsequent
approval role are based on attributes directly from the object so I =
can't
see how these would be overwritten.
 
It's very strange especially as the problem only occurs on one client; =
the
Workflow is fine on DEV and QA clients.=20
 
> -----Original Message-----
>> From: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>@GLOBAL  On Behalf =
Of
> "Becker Stephan (extern)" <Stephan.Becker.ext at mchw.siemens.de>
> Sent: Thursday, April 11, 2002 12:35 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      AW: Role Error in Workflow
>=20
> I would think that this is a variable error. My guess would be that =
in the
> branch with the user decision, a variable that is needed later in the
> role,
> is changed or otherwise overwritten, so that the role errors. A =
careful
> look
> at the bindings and containers will probably reveal what the cause =
is.
>=20
> Hth,
> Stephan
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Louise Morgan [mailto:Louise.Morgan at Xansa.com]
> Gesendet: Donnerstag, 11. April 2002 13:14
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Role Error in Workflow
>=20
>=20
> We're working on 4.6B of Connect and Go and have an issue with a =
Workflow
> to
> support Expense Approvals on the Production client.
>=20
> The Workflow starts correctly but when it gets the approval step =
which has
> a
> Role (based on a function module) it errors.  The error log shows =
that no
> agent is found and Role AC9xxxxx cannot be resolved.  However, when =
the
> Workflow is manually restarted from transaction SWPR, the role =
resolves
> correctly and the user decision task is routed to the right agent =
without
> any problems.
>=20
> Prior to the approval step, there is a condition step that evaluates
> whether
> the expenses must first be checked by an administrator.  If it =
doesn't
> have
> to be checked by the administrator the Workflow moves straight on to =
the
> approval step otherwise a user decision task is routed to the
> administrator.
> It is only when the Workflow takes the branch via the administrator =
that
> it
> errors on the approval role following completion of the check.  Going
> directly from the condition step to the approval step does not result =
in
> an
> error.
>=20
> The approval Role always resolves correctly when it is tested via =
PFAC so
> I
> do not believe there is an Organisational issue.
> The Workflow is correctly passing in the container elements the Role
> requires.
> We have tried creating a new Workflow definition and re-transporting =
which
> has not resolved the problem.
> The Workflow was fully tested in DEV & QA clients without issue.
>=20
> Can anyone shed any light on what the problem might be?