Business Object BUS2012

[Soady, Phil]

Hi Kenn,
CALL TRANSACTION performs an authorisation check S_TCODE,
based on a profile parameter.
 
See RZ10 "auth/* " profiles. I don't suggest playing with them !
THINK 57 times before changing defaults here!
 
In SU24 you can see the auth objects that will be tested.
You could in a special case turn  S_tcode off for a transaction.
This is the same as given everyone object S_TCODE for the transaction.
Nothing really gained !
 
 
IF you are throwing them into me23, why shouldn't they have me23 ?
Doesn't make sense to me.  Remember that Pgrg Comp Code etc can still be
a restriction.
 
The user can of course display any PO in his/her PGRP once inside me23  ie menu option "other document".
So what you intend to achieve may not be possible anyway.
 
if it is ME23 only, and you have super strict security issues,
make a custom display PO method on a delegated object to bus2012,
that shows the details of the PO.
 
hth
 
 
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
-----Original Message-----
From: Kenneth Hill [mailto:SAP_DEV_WB at Yahoo.com]
Sent: Thursday, 16 January 2003 9:49 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Business Object BUS2012
 
Hi SAP_WUGgers,
 
We have changed the default Display method for object Purchase Order -
BUS2012 to display our custom "Display PO" screen in place of using SAP's
standard ME23.  We made this change in our current productive system, SAP
4.0b.  In our upgraded SAP 4.6c test system, we get error "WL 210" when we
click the "Purchase Order" object in the preview panel of the Business
Workplace (WF Inbox).
 
The error message reads:
"Error triggering default method for object 0007122823
  Message no. WL 210".
 
We have narrowed the problem to an auth. object check on transaction
ME23.  We have commented out the code from the Display method, yet we
continue to get the auth check error.  The error disappears when we add the
transaction ME23 to the authorization profile and the correct "PO Display"
screen is displayed.  We are unable to determine where this auth check is
being performed.
 
Thanks for any assistance with this.
 
Kenn Hill
WF Admin
The World Bank
 
The custom ABAP code we are using for the Display method for object
Purchase Order - BUS2012 is:
 
BEGIN_METHOD DISPLAY CHANGING CONTAINER.
*  SET PARAMETER ID 'BES' FIELD OBJECT-KEY-PURCHASEORDER.
*  CALL TRANSACTION 'ME23' AND SKIP FIRST SCREEN.
 
   CALL FUNCTION 'Z_WFR_PO_APP_I'
        EXPORTING
             EBELN               = OBJECT-KEY-PURCHASEORDER
             ACTION              = ' '.
*           AGENT               =
*           RELEASE_CODE        =
*           SUBJECT             =
*      TABLES
*           COMMENTS            =
 
END_METHOD.