BOR Creation Vs Copying

Fri Dec 8 03:39:38 EST 2006

Thanks you for you imput I appreciate them.

Regards

Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext.  : 32645
Direct Line    : +27 031 910 2645
Fax                 : +27 031 902 9633
E-mail            : ngovender4 at toyota.co.za

=============================================
       Never test the depth of the water with both feet.
=============================================

             "Kjetil Kilhavn"                                              
             <KJETILK at statoil.                                             
             com>                                                       To 
             Sent by:                  "SAP Workflow Users' Group"         
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 

                                                                   Subject 
             2006/12/08 10:22          RE: BOR Creation Vs Copying         
             AM                                                            

             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
             <sap-wug at mit.edu>                                             

If it *is* a subtype you should create a subtype. If it isn't you
shouldn't.

A horse and a dog has some common features; having four legs, fur, a tail,
and being able to pull a sled. Dog is not a subtype of a horse. So you
should copy the horse object type to create a new "root" object type for
dog (unless they are both defined as subtypes of e.g. mammal). However, a
pony is a subtype of a horse, so you should create a subtype and definitely
not make a copy.

In the same manner, even if, say application for vacation has some common
features with application for a new pencil sharpener, they are completely
unrelated. They may both support an interface for applications (which
according to Shai Agassi should have one method: reject), but that is as
close as they get. You create a copy. The problem is of course that in real
life it is sometimes not that easy to determine whether it is a subtype or
not, and which choice makes most sense can depend on your point of view.

When it comes to sexiness I'd still vote for Claudia Schiffer instead of
both subtyping and copying, but we all have different tastes ;-)
--
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP

 From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
 Of Mark Pyc
 Sent: Thursday, December 07, 2006 3:33 PM
 To: SAP Workflow Users' Group
 Subject: Re: BOR Creation Vs Copying

 G'day Nat,

 A copy is a static duplicate as at the time you perform the copy. All code
 will live inside the copy.

 A subtype is a more complex OO concept. In this case it is not a copy, but
 an extensible reference to the parent. All the parents code (other than
 the definition of the key) remains in the parent objects program and the
 subtype simply access it from the there. Any new methods or attributes
 code will be in the subtype's program. This way if SAP provides fixes or
 extensions to the original object your subtype INSTANTLY has access to
 those fixes or extensions.

 Subtyping is way sexier than copying!

 Have fun,
 Mark

 On 12/7/06, Nat 4 Govender <ngovender4 at toyota.co.za> wrote:
  Hi all,

  What is the difference of creating a subtype of a BO VS copying a BO?

  Regards

  Nat Govender
  Toyota South Africa
  IT - SAP Workflow Specialist
  Internal Ext. : 32645
  Direct Line : +27 031 910 2645
  Fax : +27 031 902 9633
  E-mail : ngovender4 at toyota.co.za

  =============================================
  Never test the depth of the water with both feet.
  =============================================

  This message is a privileged and private communication
  and may be read,copied and used only by the intended recipient(s).
  If you are not an intended recipient, please let us know by return
  email. Please then delete the message and do not disclose its
  contents to any person. Neither the sender nor Toyota South Africa
  Motors accepts any liability whatsoever as a result of the further
  dissemination of this message. Whilst all reasonable steps are
  taken to avoid corruption of data or information, we do not accept
  any liability should such corruption occur.

  _______________________________________________
  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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061208/3b2b55bd/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061208/3b2b55bd/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic15881.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061208/3b2b55bd/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061208/3b2b55bd/attachment-0002.gif