Hi Rick<br><br>We had similar issues with HR related items as well like infotype updates. We got exactly the same auth error.<br>Let us know if you come with with a fix.... :)<br><br>Cheers<br>Ravi<br><br><div class="gmail_quote">
On Mon, Jun 21, 2010 at 2:04 AM, <span dir="ltr"><<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Send SAP-WUG mailing list submissions to<br>
<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SAP-WUG digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Link to BUS2009 object not working in workitem (Rick Bakker)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 20 Jun 2010 12:14:34 +0800<br>
From: Rick Bakker <<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>><br>
Subject: Re: Link to BUS2009 object not working in workitem<br>
To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
Message-ID:<br>
<<a href="mailto:AANLkTilKyY-AHI8d-o9iBeOKwxML5RaM7a2mOZUAxagU@mail.gmail.com">AANLkTilKyY-AHI8d-o9iBeOKwxML5RaM7a2mOZUAxagU@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi Workflowers,<br>
<br>
Thanks for all the suggestions. I will get to the bottom of this and<br>
report back!<br>
At the moment it looks like there's an authorization missing or a<br>
setting set wrong which causes fm MMPUR_REQUISITION_DISPLAY (called by<br>
the Display method of BUS2009) to choose tx ME53 instead of ME53N.<br>
The users don't have authorization to run ME53 (this shows up in ST01)<br>
and that's the way it should be. Now just have to find out why it's<br>
doing this.<br>
<br>
cheers<br>
Rick Bakker<br>
Hanabi Technology<br>
<br>
<br>
On Sun, Jun 20, 2010 at 12:09 AM, Mike Pokraka<br>
<<a href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>> wrote:<br>
> Hi Rick,<br>
><br>
> You are completely right SWIA is complete overkill and should never be<br>
> given to everyone.<br>
> The issue with SU53 is that it will report the last failed check. The<br>
> workflow system will sometimes check several authorisations before<br>
> failing. I think you can figure out where this is leading...<br>
><br>
> Do an auth trace with SM05 instead.<br>
><br>
> Cheers,<br>
> Mike<br>
><br>
><br>
> On Thu, June 17, 2010 11:16 am, Rick Bakker wrote:<br>
>> Hello,<br>
>><br>
>> Thanks for the responses. I tried the personal workflow settings but<br>
>> no luck. Haven't tried the authorizations yet.<br>
>><br>
>> Isn't it a bit dangerous to give everyone SWIA access?<br>
>><br>
>> thanks!<br>
>> Rick Bakker<br>
>> Hanabi Technology<br>
>><br>
>>> Try assigning the below authorization to all User Roles<br>
>>><br>
>>> Object S_TCODE<br>
>>> ?for field SWO_ASYNC<br>
>>> and<br>
>>> AUTH - - - S_TCODE RC=0 TCD=SSC1;<br>
>>> AUTH - - - S_TCODE RC=0 TCD=SSC0;<br>
>>><br>
>>> Alternately , you can check the workaround below :<br>
>>><br>
>>> In the personal workflow settings , Check the check box "Double Clicking<br>
>>> on<br>
>>> an object displays the object in the same window " .<br>
>>><br>
>>>><br>
>>>> to open the link the user indeed needs authorisation for transaction<br>
>>>> SWIA.<br>
>>>> I had the same issue and when the authorisation for transaction SWIA<br>
>>>> was<br>
>>>> given to the users everything worked fine.<br>
>>>><br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
End of SAP-WUG Digest, Vol 67, Issue 56<br>
***************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Best Regards<br>Ravi Dixit<br>