Possible Agents not recognized

Schroeter, Brad BSchroeter at ti.com
Tue Feb 15 11:07:59 EST 2000


Kenny,
Are you saying that SAP automatically runs a job once a day to refresh the
organizational environment?  If so, do you know any details about the job
(i.e. name)?
 
Thanks,
Brad
 
-----Original Message-----
From: Quenzer, Kenneth [mailto:QUENZEKD at oge.com]
Sent: Friday, February 04, 2000 1:59 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Possible Agents not recognized
 
 
Hi Robyn,
 
Whenever I have had this problem I have been able to fix it by having the
user who is the selected agent refresh the organizational environment from
their userid.  They need to do the refresh from their workflow inbox menu
(Edit --> Refresh org.environment) not from their inbox menu (Edit -->
refresh).
 
I believe that there is a job that runs once a day to do the refresh
automatically.
 
Hope this helps,
Kenny
 
-----Original Message-----
From: Robyn Davey [mailto:rdavey at omnilogic.com]
Sent: Friday, February 04, 2000 1:44 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Possible Agents not recognized
 
 
Hi,
 
I'm working in a 4.5B system.  I've defined the 'Possible Agents' of a task
as a
security 'Activity Group'.  When I trigger the workflow, all work item
runtime
reports indicate that the proper selected agent (derived via role
resolution)
has been determined from the correct pool of possible agents.  The selected
agent receives the work item in their inbox.  However, when they attempt to
execute the work item, they receive the error:
 
WL844:  Work Item xxx: User XXXX cannot reserve the work item.     (Note:  I
have been refreshing the org environment!)
 
I have found the root of the problem to be the Possible Agents definition.
If I
change the configuration from Activity Group to a General Task, the task can
be
executed successfully in the Inbox.   (Not to mention that if I change the
configuration back to Activity Group - it now works, i.e. no consistency).
 
We also have a 4.0B training system that we applied 13 4.0B hot packages.
We
have a similar configuration with the Possible Agents defined as an HR
Organizational Unit and the Selected Agents derived using Role Resolution.
We
have encountered the same error.  The problem is random and intermittent -
not
all students encounter the problem.  It almost appears that one of those hot
packages has the bug in it.
 
Has anyone else experienced this situation?
 
Thanks in advance.
 
Robyn Davey
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20000215/abbb0f1f/attachment.htm


More information about the SAP-WUG mailing list