<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=247064920-19062007><FONT face=Arial
color=#0000ff size=2>I don't know the answer, but here is what I found on SDN.
My experience has only been with BOR object, creating new, and extending
existing ones. Hope this helps!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007>BOR objects is the
category that have been around for a long time, while CL is a (relatively) new
possibility. You should use whatever is more practical in each case. For
instance, if you are working with employees and everything you need is in BOR
object BUS1065 it makes sense to use that BOR object. If you find a class that
has everything you need it makes (even more) sense to use that.<BR><BR>If you
have to create a completely new object type you should try to create a class
instead of a new BOR object. If you simply need a little bit of additional
functionality or a new virtual attribute, <U>my</U> recommendation would be to
extend the object type that exists instead of trying to create a class that
extends a BOR object. </SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007><FONT face=Arial
color=#0000ff size=2>and,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007><STRONG>ABAP
CLASS<BR></STRONG>Template for objects in ABAP Objects. Defined using CLASS -
ENDCLASS either globally in a class pool or locally in another ABAP program. The
definition of a class is made up of a declaration section for the declaration of
theclass components and animplementation section for the implementation of the
methods.<BR><B>BOR-OBJECT TYPES</B><BR>mySAP Technology service and directory of
all object types (business object types, organization object types and technical
object types) in hierarchical order.<BR>The object types are each assigned to a
packet (and thus indirectly also to an application component).<BR>Directory of
all object types in hierarchical order.<BR>The object types are each assigned a
development class (and thus indirectly also to an application
component).</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=247064920-19062007></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Albina
Fernando<BR><B>Sent:</B> Monday, June 18, 2007 1:41 PM<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> Difference between Business object method and
ABAP class methods in atask<BR></FONT><BR></DIV>
<DIV></DIV><FONT face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif"
size=2>
<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV> Can anyone tell me the difference between using Business Object
method and Class methods in the tasks of the Workflow. For eg. When creating a
task we have 2 options. Either Assign a Business Object method or a ABAP Object
class method. So I need to know the difference between the two. And also the
advantages of using the two...</DIV>
<DIV> Thanks a lot for all ur support.</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV>Albina<BR></DIV>
<DIV><BR></DIV></FONT>This email may contain confidential or privileged
information for the intended recipient(s). If you are not the intended
recipient, please do not use or disseminate the information, notify the sender
and delete it from your system.
Thanks<BR><BR>______________________________________________________________________<BR><br><br><table bgcolor=white style="color:black"><tr><td><br><br>
<br>
<br>
<br>
<br>
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --<br>
<br>
This e-mail and any files transmitted with it may<br>
contain privileged, confidential, or proprietary information<br>
which may be protected from disclosure under law, and is<br>
intended solely for the use of the individual, group, or entity<br>
to whom this e-mail is addressed. If you are not one of the<br>
named recipients, please notify the sender by e-mail and<br>
delete this message immediately from your computer. Any<br>
other use, retention, dissemination, forwarding, printing, or<br>
copying of this e-mail is strictly prohibited. Thank you for<br>
your assistance.<br>
</td></tr></table></BODY></HTML>