ZOBJECT TYPES

Kjetil Kilhavn KJETILK at statoil.com
Wed Dec 13 11:14:56 EST 2000


Why would you make a copy if you are not going to change anything? I can't think
of any other reason than fear of SAP breaking backwards compability when they
are updating the object. The less you meddle with, the less maintenance you have
to do. Of, course a consultant who sees the market becoming worse would
recommend building everything from scratch :-)
--
Kjetil Kilhavn
 
 
 
 
From:  "Nobles, Diane" <nobles_dh at nns.com>@MITVMA.MIT.EDU> on 13.12.2000 16:49
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:    SAP-WUG at MITVMA.MIT.EDU
cc:     (bcc: Kjetil Kilhavn)
Subject:  ZOBJECT TYPES
 
 
Hi guys (implied gals too), great site.  Lots of information.  I need
verification on something.  In all my training we used a copy of the SAP
delivered object types, i.e., ZBUS2001, in lieu of BUS2001, etc.,  Now that
we are creating standard tasks, I want to make sure that we need to make
this copy.  What is a rule of thumb.  Should we in fact make a copy of any
object type we use or only in the case of when we want to modify the object?
Or should we copy the objects at all?
 
Diane H. Nobles
SDE PM Team
0-7250
 
-------------------------------------------------------------------
Statoil: 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.
 


More information about the SAP-WUG mailing list