BOR Types and ABAP Classes

[Peter Carroll]

David,
            ABAP objects are much easier to use than the BOR. They are,
however, a bit diferent in that they are alomost OO in nature. The Create
private error simply means that the Superclass has a method to create
itself. This is a mechanism to control the creation of classes. You will
find that the superclass will have a method to allow creation. Simply call
this method and it will return, most likely, a reference to the object you
need.
 
As for the private attributes - well they are private to the superclass and
you cannot use them. You should really not need to if the superclass has
been designed correctly - you will probably find that they can be accessed
via methods. If you copy the class you can change anything but this is more
than likely not the way to go.
 
Regards Peter Carroll

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Bibby, David
Sent: Friday, 10 June 2005 23:36
To: SAP Workflow Users' Group
Subject: BOR Types and ABAP Classes



Hello All, 
I've never used workflows with ABAP classes before but I am currently
implementing a SAP standard workflow that uses just such a thing.

However I need to make changes to this class. 
I have created a subclass and defined it's superclass as the one the
workflow uses. 
However, as the attributes of the superclass are Private they seem to be
unavailable to my subclass. 

Also when I try to activate my subclass I get the error 
"The superclass has the property 'CREATE PRIVATE'. You cannot create an 
instance of the subclass. This can only be changed if the subclass is a

friend of the superclass.       "       

Making the subclass a friend of the superclass would be making a SAP
modification. 

As there appears to be no delegation like there are with BOR Types, how are
we supposed to use/extend standard SAP ABAP Classes ?

Many Thanks 
David 

_______________________________________________ 

This message is confidential. It may also be privileged or otherwise
protected by work product immunity or other legal rules. If you have
received it by mistake please let us know by reply and then delete it from
your system; you should not copy it or disclose its contents to anyone. All
messages sent to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are not secure
and cannot be guaranteed to be error free as they can be intercepted,
amended, lost or destroyed, or contain viruses. Anyone who communicates with
us by email is taken to accept these risks. 



The contents of any email addressed to our clients are subject to our usual
terms of business; anything which does not relate to the official business
of the firm is neither given nor endorsed by it. 



The registered address of the UK partnership of Linklaters is One Silk
Street, London, EC2Y 8HQ. Please refer to
http://www.linklaters.com/regulation for important information on the
regulatory position of the firm. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050613/4fbdecd5/attachment.htm