Authorizations for Role Resolution

[Susan R. Keohan]

Thanks Paraj, Phil, Jocelyn, and Mark.
 
In our case, we have decided to give the users the authorizations required (Basis, not structural,
although I have no doubt those will come to bite us later on) so that we do not have to de-select
the "Advance with Dialog', when this is a real feature that we might want to use.
 
While I do understand the problem, and also how to get around it, it seems to me from reading some
OSS notes that SAP is trying to fix this 'feature' (notes 401829, 308679, for example, although
these refer to background steps, the symptoms appear to be related).  Does anyone know if I am
correct in assuming that SAP is trying to do this ?  It would be a great relief to know in the
future that this feature would be eliminated.
 
Thanks again,
Sue
 
PS: Thanks also to Phil for helping people learn to fish (through the archives!)
 
Griffiths, Mark wrote:
> Sue,
>
> You have found a little known workflow 'feature' I discovered last year:
>
> Role resolution for the subsequent step (and interestingly any conditions in the workflow) are all carried out using the userid of the previous user.  So, user 1 must have all the authorisations required to find user2.
>
> SU53 should tell you which authorisations have failed.
>
> If you can't add the authorisations to your users then the only way around this is to insert a background step which does nothing in between your two dialog steps to switch the user evaluating the role to WF-BATCH.
>
> Cheers,
>
> Mark
>
> -----Original Message-----
>> From: Susan R. Keohan
> To: SAP-WUG at MITVMA.MIT.EDU
> Sent: 02/07/2003 21:58
> Subject: Authorizations for Role Resolution
>
> Hello all,
>
> I have a workflow that has two dialog tasks with no intervening
> background tasks.  When User1
> executes the first task, the workflow fails on the role resolution of
> the second task ('5W 170 -
> structure 1 S 600028118 WF_ORGUS. No Agent Found.'). This role
> resolution uses some standard SAP
> functions to climb up and down the org structure.
>
> The role resolution works fine when I test the role.  The workflow can
> process if I am the user
> executing the first task.  The workflow can also proceed if I execute
> SWPR to restart the workflow
> in error.
>
> I had the Basis folks give User1 SAP_All and SAP_New (for a limited
> time!) and found that the error
> went away. That is, User1 executed his dialog task, and the role
> resolution for the second task was
> fine, the task was delivered to the appropriate user.  So we know that
> this is an authorization issue.
>
> However, the question in my mind is, why would the authorizations of
> User1 have an impact on the
> role resolution of the subsequent dialog task ?  Shouldn't that role
> resolution be carried out under
> the auspices of WF-Batch ?
>
> Thanks in advance,
> Sue
> --
> Susan R. Keohan
> SAP Workflow Developer
> MIT Lincoln Laboratory
> 244 Wood Street
> LI-200
> Lexington, MA. 02420
> 781-981-3561
> skeohan at mit.edu
 
 
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
skeohan at mit.edu