<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1499" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=058490200-13062005><FONT face=Arial color=#0000ff
size=2>David,</FONT></SPAN></DIV>
<DIV><SPAN
class=058490200-13062005>
<FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=058490200-13062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=058490200-13062005><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=058490200-13062005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=058490200-13062005><FONT face=Arial color=#0000ff
size=2>Regards Peter Carroll</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>Bibby, David<BR><B>Sent:</B> Friday, 10 June 2005 23:36<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> BOR Types and ABAP
Classes<BR><BR></FONT></DIV><!-- Converted from text/rtf format -->
<P><FONT face="Trebuchet MS" size=2>Hello All,</FONT> <BR><FONT
face="Trebuchet MS" size=2>I've never used workflows with ABAP classes before
but I am currently implementing a SAP standard workflow that uses just such a
thing.</FONT></P>
<P><FONT face="Trebuchet MS" size=2>However I need to make changes to this
class.</FONT> <BR><FONT face="Trebuchet MS" size=2>I have created a subclass
and defined it's superclass as the one the workflow uses.</FONT> <BR><FONT
face="Trebuchet MS" size=2>However, as the attributes of the superclass are
Private they seem to be unavailable to my subclass.</FONT> </P>
<P><FONT face="Trebuchet MS" size=2>Also when I try to activate my subclass I
get the error</FONT> <BR><I><FONT face="Trebuchet MS" size=2>"The superclass
has the property 'CREATE PRIVATE'. You cannot create an
</FONT></I><BR><I><FONT face="Trebuchet MS" size=2>instance of the subclass.
This can only be changed if the subclass is a
</FONT></I><BR><I><FONT
face="Trebuchet MS" size=2>friend of the
superclass.
"</FONT></I> </P>
<P><FONT face="Trebuchet MS" size=2>Making the subclass a friend of the
superclass would be making a SAP modification.</FONT> </P>
<P><FONT face="Trebuchet MS" size=2>As there appears to be no delegation like
there are with BOR Types, how are we supposed to use/extend standard SAP ABAP
Classes ?</FONT></P>
<P><FONT face="Trebuchet MS" size=2>Many Thanks</FONT> <BR><FONT
face="Trebuchet MS" size=2>David</FONT> </P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'">_______________________________________________
</SPAN></P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'">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.
</SPAN></P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'"></SPAN></P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'">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. </SPAN></P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'"></SPAN></P>
<P style="MARGIN-TOP: 0pt; MARGIN-BOTTOM: 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: 'Arial'">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. </SPAN></P></BLOCKQUOTE></BODY></HTML>