<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1480" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2>Edwin,</FONT></SPAN></DIV>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2>We are running xRPM (Resource and Portfolio Management XApp) version 2
SP5.</FONT></SPAN></DIV>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2>It seems like if I want to extend this class by creating a subclass I'll
have to replace the superclass with the subclass throughout the workflow,
although as I'm getting the error anyway I might as well create my own BO
through SWO1.</FONT></SPAN></DIV>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=490585615-10062005><FONT face="Trebuchet MS" color=#800000
size=2>David</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader 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>Edwin
Mukusha<BR><B>Sent:</B> 10 June 2005 16:52<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> Re: BOR Types and ABAP
Classes<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Dear
David,</FONT> <BR><BR><FONT face=sans-serif size=2>I am curious. What
version of SAP are you running? This will be factor on whether you need
to even worry about ABAP Classes in workflow. For example we are on
Enterprise 4.7 Ext set 2.00 and ABAP Classes are not supported in the workflow
environment fully. :-( ......sigh.</FONT> <BR><BR><BR><FONT
face=sans-serif size=2>Edwin.</FONT> <BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<TD><FONT face=sans-serif size=1><B>"Bibby, David"
<david.bibby@linklaters.com></B></FONT> <BR><FONT face=sans-serif
size=1>Sent by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>06/10/2005 10:36 AM</FONT> <BR><FONT
face=sans-serif size=1>Please respond to "SAP Workflow Users'
Group"</FONT> </P>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
"SAP Workflow Users' Group" <sap-wug@mit.edu></FONT>
<BR><FONT face=sans-serif size=1> cc:
</FONT> <BR><FONT face=sans-serif size=1>
Subject: BOR Types and
ABAP Classes</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT face="Trebuchet MS"
size=2>Hello All,</FONT><FONT size=3> </FONT><FONT face="Trebuchet MS"
size=2><BR>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><FONT face="Trebuchet MS" size=2>However I need to make changes to this
class.</FONT><FONT size=3> </FONT><FONT face="Trebuchet MS" size=2><BR>I have
created a subclass and defined it's superclass as the one the workflow
uses.</FONT><FONT size=3> </FONT><FONT face="Trebuchet MS" size=2><BR>However,
as the attributes of the superclass are Private they seem to be unavailable to
my subclass.</FONT><FONT size=3> </FONT>
<P><FONT face="Trebuchet MS" size=2>Also when I try to activate my subclass I
get the error</FONT><FONT size=3> </FONT><FONT face="Trebuchet MS"
size=2><I><BR>"The superclass has the property 'CREATE PRIVATE'. You cannot
create an <BR>instance of the subclass. This can only be changed if the
subclass is a <BR>friend of the superclass.
"</I></FONT><FONT size=3> </FONT>
<P><FONT face="Trebuchet MS" size=2>Making the subclass a friend of the
superclass would be making a SAP modification.</FONT><FONT size=3> </FONT>
<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><FONT face="Trebuchet MS" size=2>Many Thanks</FONT><FONT size=3>
</FONT><FONT face="Trebuchet MS" size=2><BR>David</FONT><FONT size=3>
</FONT><BR><FONT face=Arial
size=1>_______________________________________________ </FONT><BR><FONT
face=Arial size=1>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. </FONT><BR><FONT face=Arial size=1>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. </FONT><BR><FONT face=Arial
size=1>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. </FONT><FONT
size=2><TT>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></TT></FONT><BR></P></BLOCKQUOTE></BODY></HTML>