<div>Hi Swathi ,</div> <div> </div> <div>SWIA is a transaction which should be used only by WF administrator and should not be given to end users .</div> <div> </div> <div>You need to setup your WF Org. structure properly so that eack work-item goes to right person thats all .</div> <div> </div> <div>Kind Regards,</div> <div>Sudhir Chauhan<BR><BR><B><I>Swathi_Devireddy <Swathi_Devireddy@satyam.com></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Mike,<BR><BR>If my User needs to execute a workitem in SWIA there is a chance he can<BR>execute someone elses workitem.Is there a way to restrict it .<BR>Where do I do the authorization check <BR><BR>Cheers,<BR>Swathi<BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Mike Pokraka<BR>Sent: Thursday, December 14, 2006 7:52 PM<BR>To: SAP Workflow Users'
Group<BR>Subject: Re: SWIA - Transaction<BR><BR>Hello Swathi,<BR>Authorisation checks can lie. The system may try SWIA after something<BR>else<BR>has failed, but it will only show the last failed check.<BR>Give the user SWIA and then do another auth check. you should find a<BR>different object or transaction is needed, after which you can then take<BR>SWIA away again.<BR>Cheers,<BR>Mike<BR><BR><BR>On Thu, December 14, 2006 12:43, Swathi_Devireddy wrote:<BR>> Hi,<BR>><BR>><BR>><BR>> SWIA administrator<BR>><BR>> Transaction SWIA is a powerful transaction which should not be<BR>allocated<BR>> to an ordinary user. However, the s_tcode = SWIA is checked when an<BR>> approver retrieve a work item from Business Workplace for<BR>approval.User<BR>> then needs the right as Workflow Administrator to administer work<BR>items<BR>> which is undesirable. Any security mesaure can be applied?<BR>><BR>><BR>><BR>><BR>><BR>><BR>><BR>>
Regards,<BR>><BR>> Swathi Devireddy<BR>><BR>><BR>><BR>> DISCLAIMER:<BR>> This email (including any attachments) is intended for the sole use of<BR>the<BR>> intended recipient/s and may contain material that is CONFIDENTIAL AND<BR>> PRIVATE COMPANY INFORMATION. Any review or reliance by others or<BR>copying<BR>> or distribution or forwarding of any or all of the contents in this<BR>> message is STRICTLY PROHIBITED. If you are not the intended recipient,<BR>> please contact the sender by email and delete all copies; your<BR>cooperation<BR>> in this regard is appreciated.<BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>><BR><BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR><BR><BR>DISCLAIMER:<BR>This email
(including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.<BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></BLOCKQUOTE><BR><p> 
<hr size=1>Want to start your own business? Learn how on <a href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index">Yahoo! Small Business.</a>