Solved: Problems with role resolution

Uebelacker Jochen (extern) Jochen.Uebelacker at erln.gepas.de
Wed Apr 11 04:25:28 EDT 2001


Hello,=20
 
I solved my problem with the role resolution.=20
 
The cause was a mistake in the role-function module:=20
I had forgot to write the OTYPE 'US' into the actor-table . The =
complicated
at the matter was, that the actor-table was not empty, because the =
actual
user-names (OBJID) stood inside. In the sequence, also no role =
termination
applies, because the 'RAISE NOBODY_FOUND' is only released when the
actor-table is initial. In addition the simulation of the role has =
always a
result with correct agents. Only the Workflow did't work and =
distributed the
workitem at all agents.=20
 
Regards
 
Jochen =DCbelacker
T-Systems
Consultant
System Integration, EBS-SES
debis Systemhaus Dienstleistungen GmbH
 
 
-----Original Message-----
From: Uebelacker Jochen (extern)
[mailto:Jochen.Uebelacker at erln.gepas.de]
Sent: Monday, 9 April 2001 16:59=20
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problems with role resolution
 
Hi Jocelyn,
 
thank you very much for your help.
 
you are right. I didn't saw the SELECTED but the POSSIBLE agents.
But why? If want to check the agents in the workflow log, only two =
buttons
become visible: "Possible agents" and "Excluded agents". I'm missing =
the
third button "Agents". I think the reason is that no agents were found =
by
the role?!?
 
I have checked the user-ids for the agents. Everything Ok.
Now I'm going to check again the bindings between workflow step and =
role.
 
Jochen
 
-----Urspr=FCngliche Nachricht-----
Von: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Gesendet am: Montag, 9. April 2001 03:49
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Problems with role resolution
 
Hi Jochen,=20
Are you sure you are looking at SELECTED agents (the result of the =
role)
and not POSSIBLE agents (who CAN perfom the task).=20
 
If you are, then consider the following:
 
Role termination only applies if absolutely NO agents were found by the
role.
 
If the role found someone but they were not a possible agent, then the =
role
does not terminate.  In this case, possible agents (i.e. general task =
in
your case) would
be used instead.
 
If you have tested your role and the correct agents are found, check =
that=20
they have userids - i.e. that you are not just finding the correct
jobs/positions/etc.=20
but no userid has been assigned to them.  If I remember correctly, the =
4.6C
role resolution
simulation allows you to check that userids are attached to the agents
found.=20
 
And of course, double-check your bindings between your workflow step =
and
your role.
 
P.S. If you had just set up your agents, you might want to run SWU_OBUF =
to
update
the HR buffers just in case.=20
 
Hope that helps.
Regards,
        Jocelyn Dart=20
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)=20
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>=20
Tel: +61 412 390 267
Fax: +61 2 9935 4880
=20
 
 
-----Original Message-----
From: Uebelacker Jochen (extern)
[mailto:Jochen.Uebelacker at erln.gepas.de]
Sent: Friday, 6 April 2001 5:52 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problems with role resolution
 
 
Hi all,
 
In a Workflow-Step (Method BUS2081.DISPLAY) I use a function module for =
role
resolution. =20
The task is a general task.
The worklfow works well, but if I want to see the assigned agents for =
the
step, I get Information-PopUp with following message:
 
" All user can process this task "
 
I wonder, because in the role-definition I've set the flag "Terminate =
if
role resolution has no result".
In the simulation of the role resolution I can see the corrcet agents.=20
So what is going wrong in the workflow?
We are on SAP 4.6C.
 
 
Any help is highly appreciated.=20
Thanks=20
 
Jochen =DCbelacker
T-Systems
Consultant
System Integration, EBS-SES
debis Systemhaus Dienstleistungen GmbH
 


More information about the SAP-WUG mailing list