Objects and Attachments at Workflow workplace for BUS2012

[Dart, Jocelyn]

Hi Kevin,
No you DON'T replace the object type BUS2012 in the workflow.
 
The point of delegation is that everything you use in your workflow
points to BUS2012, but the delegation makes it use your object, e.g.
ZBUS2012,
instead.   You can see this even at design time - e.g. go to task
using BUS2012, double click on object type BUS2012 and it should drill
down immediately to ZBUS2012 - that confirms your delegation is correct.
 
This also means any reports referring to object BUS2012 will then actually
use ZBUS2012 including its default method in objects and attachments
buttons.
 
If this isn't happening then your delegation isn't correct.
Make sure you are using SYSTEM-WIDE delegation not the gui specific one.
Also if you display BUS2012 in transaction SWo1 and go to basic data you
should
see that is delegating to your delegation type.
Regards,
Jocelyn.
 
-----Original Message-----
From: Kevin Yu [mailto:kevin.yu at its.monash.edu.au]
Sent: Thursday, 21 March 2002 9:50 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Objects and Attachments at Workflow workplace for BUS2012
 
 
Hi Jocelyn,
 
Thanks a lot for your advice.
 
I have checked that BUS2012 is delegated to the customised subtype as
the Delegate type is the subtype.
 
I have redefined "display" at the subtype to change the call from ME23
to ME23N.
 
There is something I have not been doing is to replace the Object type
of a Workflow.  So, I am a bit nervous.  The workflow currently is using
Object type BUS2012.  Jocelyn, how can I replace the existing Object
type from BUS2012 to the Subtype such that the "display" can be used by
the Objects and attachments Button?  I cannot find the right spot to do
it!
 
Thanks,
 
Kevin.
 
 
 
"Dart, Jocelyn" wrote:
>
> Hi Kevin,
> Make sure:
>
> BUS2012 is delegated system-wide to your customised subtype.
>
> Your customised subtype specifies your new "display" method that calls
> ME23N as the default method of the object in the basic data. Ideally
> you should "redefine" the inherited "display" method and include your
> call to ME23N in the redefined method.
>
> Once your subtype and method is being used instead of the standard object
> type and method
> the authorization issue should no longer occur.
>
> Regards,
>         Jocelyn Dart
> Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
> SAP Australia
> Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
> Tel: +61 412 390 267
> Fax: +61 2 9935 4880
>
> -----Original Message-----
>> From: Kevin Yu [mailto:kevin.yu at its.monash.edu.au]
> Sent: Thursday, 21 March 2002 12:56 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Objects and Attachments at Workflow workplace for BUS2012
>
> Hi,
>
> I am currently working on 40B upgrade to 46C.  I have a few questions on
> the workflow upgrade concerning PO release workflow.  I have a
> customised sub object type using BUS2012 as supertype for the PO release
> workflow.
>
> 1. It seems that when click on Objects and Attachments button at
> Workplace (Workflow), Method "Display"
>    of BUS2012 will be executed.  The method is calling Transaction
> ME23.  Using Enjoy screen is the
>    standard here at Monash.  So, I would like to create a new Method at
> the customised sub object type
>    cloning "Display" to call transaction ME23N.  The question is how do
> I link the Objects and
>    Attachments button to the new Method instead of "Display?
>
> 2. We are taking tcode authorisation ME23 away.  So nobody can access
> ME23 but ME23N.  However, it seems
>    ME23 is always required for the Objects and Attachments button to
> work otherwise an error message
>    WL 210 "Error triggering default method for object "PO number"" will
> come up.  I have changed the          "Display" method to call ME23N and
> no code in the Object program has ME23.  This error message still
> comes up unless tcode ME23 authorisation is given then the error will be
> disappeared.  Where is the       authorisation check on tcode ME23
> coming from?  How can I get rid of it?
>
> 3. How can I get rid of the "Tips and tricks" at the Workflow Workplace.
>
> Thank you in advance!
>
> Regards,
>
> Kevin.