WF_TASK ALLAGENTSOFTASKGETANDDISPATCH

Thu May 12 12:54:49 EDT 2005

Hmmmm..

I had a strange situation a couple of weeks ago. On a Sunday our FI team  had 
suddenly decided on some special processing and requested that all  users be 
locked out of the production system. There was one user already in the  system 
before the lockout and was able to continue working most of the day and  
triggered several workflows. The workflows triggered before the lockout started  
but the ones triggered later did not start. SM58 list displays the "User is  
locked. Please notify the person responsible" for the locked user id for  
function module SWW_WI_CREATE_VIA_EVENT_IBF. Target system is  WORKFLOW_LOCAL...The 
WF-BATCH id was not locked. 

Why is the WF initiator id being validated for creating a WF  instance??

Regards,
Ramki Maley
Workflow Developer,  USCBP.
248-613-1287 (C)

In a message dated 5/12/2005 9:56:13 AM Eastern Standard Time,  
keohan at ll.mit.edu writes:

Well,  for what is is worth, OSS has stated that:
> From my understanding  BC-BMT-WFM layer
> does not perform any checking in order to prevent a  Workitem being
> delivered to a Agent which User is Locked: USR02-UFLAG  (User Lock
> Status).

It seems counter-productive to me that I am  allowed to route a workitem to a 
user who is locked and 
delimited.   Is this just me ?  Of course, there are  work-arounds, but if 
anyone  else has 
experienced this problem, I would be interested to hear how you  dealt with 
it.

Thanks,
Sue

Susan R. Keohan wrote:

>  Hi Mike,
> 
> What's interesting is that in our Dev environment,  which is not 
> necessarily the best place for testing :), I've had the  following 
> results...
> 
> USERID_A, name John Smith, no  PA0105 record, can be selected either by 
> userid or by last name in  the drop-down.
> 
> USERID_B, name Michael Doe, with valid PA0105  record, can be chosen by 
> entering USERID_B in the entry screen, but  *not* by entering 'Doe' in 
> the drop-down.
> 
> USERID_C,  name Mark Jones, with delimited PA0105 record, can be chosen 
> by  entering USERID_C in the entry screen, and also by entering 'Jones' 
>  in the drop-down.
> 
> Of course, it would be nice if I had  consistent data in Dev to work 
> with.  I suspect I need to spend  some quality time with OSS.
> 
> Thanks!
> Sue
>  
> Michael Pokraka wrote:
> 
>> Hi Sue, If you manually  delimit 105, does it behave as expected? If so 
>> it should  become
>> a query for the HR people rather than user  admin/workflow.
>> I'm curious, so could you let us know the outcome?  Cheers
>> Mike
>>
>> --- "Susan R. Keohan"  <keohan at ll.mit.edu> wrote:
>>
>>> Hello  WF'ers,
>>>
>>> We are on 4.6c, Support Pack level  39.  We have used the wizard 'Choose
>>> Agent' to provide a  dialog box to certain users(Agents A)  which will 
>>> allow  them to choose the next
>>> agent(Agents B) in a subsequent  workflow step.  This creates a task 
>>> which calls the  method
>>> ALLAGENTSOFTASKGETANDDISPATCH of object WF_TASK, which,  in turn, 
>>> calls function module
>>>  SWU_WF_TASK_DISPATCH.
>>>
>>> However, I've discovered  that Agent A may enter, or select via the 
>>>  dropdown,
>>> a last name or username of for Agent B, whose SAP  UserID is locked 
>>> and delimited (but not deleted). I've  examined the SU01D records, and 
>>> they are indeed locked and  delimited, the personnel records are
>>> 'withdrawn' and  delimited, but the PA0105 infotype records are *not* 
>>>  delimited.
>>>
>>> It's unfortunate for Agent A that  they can select people (Agent B) 
>>> who are no
>>>  longer here.  I'm about to enter an OSS message, but thought I would  
>>> try our experts on the
>>> SAP-WUG first.   Has anyone come across this error before ?
>>> -- 
>>>  Susan R. Keohan
>>> SAP Workflow Developer
>>> MIT  Lincoln Laboratory
>>> 244 Wood Street
>>>  LI-200
>>> Lexington, MA. 02420
>>>  781-981-3561
>>> keohan at ll.mit.edu
>>>
>>>  _______________________________________________
>>> SAP-WUG  mailing list
>>> SAP-WUG at mit.edu
>>>  http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>
>>
>>  Michael Pokraka
>> Workflow Connections Ltd.
>> Tel.: +44  (0)7786 910 855
>>  _______________________________________________
>> SAP-WUG mailing  list
>> SAP-WUG at mit.edu
>>  http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
> 

--  
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244  Wood Street
LI-200
Lexington, MA.  02420
781-981-3561
keohan at ll.mit.edu
_______________________________________________
SAP-WUG  mailing  list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

Regards,
Ramki Maley
Workflow Developer,  USCBP.
248-613-1287 (C)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050512/c2a937e3/attachment.htm