Subtype of Business Object Type

Fri Aug 26 08:11:45 EDT 2005

Mike correctly answered why you can only have one delegated subtype.  The purpose of still allowing multiple subtypes to exist, even though none of them would be considered "extensions" of the original, is to give you the flexibility to modify existing methods or attributes for one of your processes without impacting other ones.  For example, say your business creates sales orders for some funky process that differs from ordinary sales orders.  You'd like to use most of the BUS2032 functionality, but need to make changes to BUS2032->CreateFromDat2 for this one scenario.  You don't, though, want these changes to affect your "normal" sales order process.  One option would be to create an un-delegated subtype for BUS2032, say ZBUS203299 and then make your changes to CreateFromDat2.  Assuming you already had, say a ZBUS2032 subtype that had been delegated to BUS2032, you would leave all references to BUS2032 alone throughout your system, except for the one scenario in which you need this changed functionality.  For that scenario, you would instead use ZBUS203299.

Have said all that, I would personally just create a new method in the delegated subtype, say MyCreateFromData, that performs the desired functionality.  I'm sure somewhere out there someone has encountered a need for multiple subtypes that actually makes sense, unlike this contrived example!

Hope that explains things a bit,
David  

 -----Original Message-----
From: 	sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]  On Behalf Of Mike Pokraka
Sent:	Friday, August 26, 2005 3:14 AM
To:	SAP Workflow Users' Group
Subject:	RE: Subtype of Business Object Type

Delegation is the opposite of subtyping/inheritance: making a subtype's
attributes and methods appear as if they were part of the supertype.

It would not make sense to be able to delegate more than one subtype. If
you were able to delegate two subtypes, which one would take preference if
both have attributes with the same name?

Cheers
Mike

Maorriyan wrote:
> Dear Kjetil,Jeff and David.
> Thanks for your reply and explanation.
> Guys..you already answer my questions.
> I'm wondering what's the purpose if we can create many
> subtype but only one subtype can be delegate with
> business object type.
>
> --- "Trant, David" <David.Trant at andrew.com> wrote:
>
>> I highly recommend only creating one subtype and
>> delegating it.  This
>> approach seems to be generally validated by the SAP
>> folks with whom I've
>> spoken about this topic.  Doing this saves a lot of
>> headaches with
>> regard to configuring everything with either BUSxxxx
>> or ZBUSxxxx.  The
>> delegation allows you to call your new object by the
>> old name
>> everywhere, and indeed essentially automatically
>> adds your new
>> functionality everywhere the old object is used.
>> Clearly, there might
>> be esoteric cases where this behavior is not
>> desired, but I've yet to
>> encounter any.  What I have encountered is a
>> situation where one of our
>> consultants created a subtype separate from the
>> delegated subtype and
>> over time it became more difficult to follow the
>> connections.
>>
>> Good luck,
>> David
>>
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu
>> [mailto:sap-wug-bounces at mit.edu] On Behalf
>> Of Jeff Rappaport
>> Sent: Thursday, August 25, 2005 9:03 AM
>> To: SAP Workflow Users' Group
>> Subject: RE: Subtype of Business Object Type
>>
>> Maorriyan,
>>
>>   Kjetil is correct, you can create as many subtypes
>> or
>> copies as you'd like. But in case it has any baring
>> on
>> your questions, remember you can only Delegate one
>> subtype
>> to the supertype.
>>
>> Jeff Rappaport
>> www.Business-Workflow.com
>>
>> ---- Original message ----
>> >Date: Thu, 25 Aug 2005 11:51:40 +0200
>> >From: "Kjetil Kilhavn" <KJETILK at statoil.com>
>> >Subject: RE: Subtype of Business Object Type
>> >To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>> >
>> >1. As many as you want (or should want ;-)
>> >
>> >2. A subtype only has an impact on other workflows
>> using
>> the same object
>> >type if you delegate the parent object type to the
>> subtype. And even
>> >then it only has an impact if you redefine a method
>> (or
>> attribute),
>> >otherwise the only impact is that new workflows
>> will have
>> access to the
>> >additional attributes, methods and events.
>> >--
>> >Kjetil Kilhavn, Statoil KTJ IT BKS
>> >
>> >-----Original Message-----
>> >From: sap-wug-bounces at mit.edu [mailto:sap-wug-
>> bounces at mit.edu] On Behalf
>> >Of Maorriyan
>> >Sent: 25. august 2005 10:51
>> >To: SAP Workflow Users' Group
>> >Subject: Subtype of Business Object Type
>> >
>> >Hi all,
>> >I have two questions:
>> >
>> >1.How many subtype that we can create under 1
>> object type?
>> >2.If we create subtype, will it impacting other
>> workflow
>> that using same
>> >business object type?
>> >
>> >
>> >
>> >Maorriyan
>> >
>> >Send instant messages to your online friends
>> >http://uk.messenger.yahoo.com
>> >_______________________________________________
>> >SAP-WUG mailing list
>> >SAP-WUG at mit.edu
>> >http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >
>> >
>>
>>----------------------------------------------------------
>> ---------
>> >The information contained in this message may be
>> CONFIDENTIAL and is
>> >intended for the addressee only. Any unauthorised
>> use,
>> dissemination of the
>> >information or copying of this message is
>> prohibited. If
>> you are not the
>> >addressee, please notify the sender immediately by
>> return
>> e-mail and delete
>> >this message.
>> >Thank you.
>> >
>> >_______________________________________________
>> >SAP-WUG mailing list
>> >SAP-WUG at mit.edu
>> >http://mailman.mit.edu/mailman/listinfo/sap-wug
>> >
>> >
>> Jeffrey A. Rappaport
>> Business Workflow, LLC
>> voice: (732)355-0123
>> fax:   (509)757-4144
>> email: Jeff at Business-Workflow.com
>> web:   www.Business-Workflow.com
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
> ------------------------------------------------------------------------------------------------
>> This message is for the designated recipient only
>> and may
>> contain privileged, proprietary, or otherwise
>> private information.
>> If you have received it in error, please notify the
>> sender
>> immediately and delete the original.  Any
>> unauthorized use of
>> this email is prohibited.
>>
> ------------------------------------------------------------------------------------------------
>> [mf2]
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> Maorriyan
>
> Send instant messages to your online friends http://uk.messenger.yahoo.com
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>

Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]