BUS2O12 in 3.1H and 4.6C

[Flavio Oliveira]

You have first to redefine the method. Goto Edit-->Redefine. Than you can
create your own code to this method.
 
Concerning the second point, if you use the event creation via change
document, you can define the same event for any type of purchasing document
created.
 
Flavio.
 
>From: "Ea, Ty" <TEa at citgo.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: BUS2O12 in 3.1H and 4.6C
>Date: Thu, 16 Aug 2001 08:11:37 -0500
>
>Mark and Flavio,
>
>Thank you for your replies.
>
>We are currently using subtype ZMBUS2012.  However, when I attempt to edit
>the method 'ExistenceCheck' on this subtype as you have suggested, it gives
>me a message the saids it is inherited from object type BUS2012 and does
>not
>allow me to change it.  Any suggestions on getting it to edit mode?
>
>Also, assuming that we can make the change to this method to include the
>document type for a contract, will the creation of a contract publish the
>same event as the creation of a purchase order as in 3.1h?  Probably not,
>but I figured it wouldn't hurt to ask.
>
>Kind regards,
>Ty
>
> > ----------
> > From:         Griffiths, Mark[SMTP:mark.griffiths at sap.com]
> > Reply To:     SAP Workflow Users' Group
> > Sent:         Thursday, August 16, 2001 7:06 AM
> > To:   SAP-WUG at MITVMA.MIT.EDU
> > Subject:      Re: BUS2O12 in 3.1H and 4.6C
> >
> > You could try creating a delegated subtype of BUS2012 and in the subtype
> > redefine the method existence check so that it doesn't just check for
> > Purchase Orders (it checks for a document type, change this statement to
> > include the outline agreement document type too).  You will also need to
> > redefine things like the display method to call the different
>transactions
> > based upon document type.
> >
> > Regards,
> >
> > Mark
> >
> > SAP UK
> >
> >
> > -----Original Message-----
> > From: Ea, Ty [mailto:TEa at citgo.com]
> > Sent: 15 August 2001 21:50
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: BUS2O12 in 3.1H and 4.6C
> >
> >
> >
> > Hello everyone,
> >
> > In version 3.1h, we are able to use object type BUS2012 - Purchase Order
> > to
> > instantiate not only purchase orders but also outline agreements.
>During
> > our tests in version 4.6c, we realized that we can no longer use object
> > type
> > BUS2012 to instantiate an outline agreement.  Has anyone encountered
>this
> > problem?  What did you do to solve this?  We would prefer not to create
> > another seperate workflow definition for outline agreements that is
> > instantiated by object type BUS2014 - Purchase contract.  Any suggestion
> > would be appreciated.
> >
> > Kind regards,
> >
> > Ty Ea
> > CITGO Petroleum Corporation
> > (918) 495-4132
> > The information transmitted is intended only for the person or entity to
> > which it is addressed and may contain confidential and/or privileged
> > material. Any review, retransmission, dissemination or other use of, or
> > taking of any action in reliance upon, this information by persons or
> > entities other than the intended recipient is prohibited. If you
>received
> > this in error, please contact the sender and delete the material from
>any
> > computer.
> >
>The information transmitted is intended only for the person or entity to
>which it is addressed and may contain confidential and/or privileged
>material. Any review, retransmission, dissemination or other use of, or
>taking of any action in reliance upon, this information by persons or
>entities other than the intended recipient is prohibited. If you received
>this in error, please contact the sender and delete the material from any
>computer.
 
 
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp