Link to BUS2009 object not working in workitem

Paul.Bakker@osr.treasury.qld.gov.au Paul.Bakker at osr.treasury.qld.gov.au
Mon Jun 21 23:54:28 EDT 2010


By the way, you can just call it Display. No need for Display2.



                                                                           
             Rick Bakker                                                   
             <rbakker at gmail.co                                             
             m>                                                         To 
             Sent by:                  "SAP Workflow Users' Group"         
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 
                                                                           
                                                                   Subject 
             22/06/2010 12:59          Re: Link to BUS2009 object not      
             PM                        working in workitem                 
                                                                           
                                                                           
             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
             <sap-wug at mit.edu>                                             
                                                                           
                                                                           




Hello Workflowers,

I don't have a fix but I do have a workaround.

To recap:
- ECC6
- custom workflow based on BUS2009 (Purchase Requisition Item)
- workitem contains link to the object instance (as per default
behaviour) in SBWP
- clicking on the link to the object instance (by regular users) has no
effect;
  expected behaviour is that it should display the PRI via tx ME53N;
  SU53 says that authorization failed on tx SWIA;
  ST01 says that authorization failed on tx ME53

My workaround is to delegate to ZBUS2009 (I was doing this anyway) and
create a method called DISPLAY2 which is an exact copy of the DISPLAY
method of BUS2009 (which calls fm MMPUR_REQUISITION_DISPLAY). This
DISPLAY2 is then set to the default method of ZBUS2009.

I have no idea why this works, but it does. A bug? I tried
regenerating BUS2009, it didn't help. Good news is that the users
don't need any extra privileges. So no need to let them have SWIA!

If anyone has any ideas on how to get the BUS2009 method working, feel
free. I'll give them a try.
I'd prefer not to change BUS2009 itself.

cheers
Rick Bakker
Hanabi Technology

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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



******************************************************************************************************************************************************

Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.

The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  

******************************************************************************************************************************************************





More information about the SAP-WUG mailing list