<!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><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007>Hi John, </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007>Actually having worked with both ABAP OO for Workflow
and BOR my current opinion is - only use BOR for eventing if you are using - a
standard workflow as-is or an event technique that doesn't support OO - like
status management events. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007>Otherwise stick with ABAP OO and link to the existing
BOR using an attribute of type SIBFLPORB. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=321370806-20062007>Best of both worlds. ABAP OO is soooooooooooooooo
much easier to use for enhancements. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Senior Consultant</FONT></SPAN> <BR><SPAN lang=en-us><B><FONT face=Arial
color=#808080 size=1>SAP Australia Pty Ltd.</FONT></B></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>Level 1/168 Walker
St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>North Sydney </FONT></SPAN><BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>NSW, 2060</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>Australia</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>T +61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>M + 61 412 390 267</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>E jocelyn.dart@sap.com</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>The
information contained in or attached to this electronic transmission is
confidential and may be legally privileged. It is intended only for the person
or entity to which it is addressed. If you are not the intended recipient, you
are hereby notified that any distribution, copying, review, retransmission,
dissemination or other use of this electronic transmission or the information
contained in it is strictly prohibited. If you have received this electronic
transmission in error, please immediately contact the sender to arrange for the
return of the original documents. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Electronic
transmission cannot be guaranteed to be secure and accordingly, the sender does
not accept liability for any such data corruption, interception, unauthorized
amendment, viruses, delays or the consequences thereof.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>Any views
expressed in this electronic transmission are those of the individual sender,
except where the message states otherwise and the sender is authorized to state
them to be the views of SAP AG or any of its subsidiaries. SAP AG, its
subsidiaries, and their directors, officers and employees make no representation
nor accept any liability for the accuracy or completeness of the views or
information contained herein. Please be aware that the furnishing of any pricing
information/ business proposal herein is indicative only, is subject to change
and shall not be construed as an offer or as constituting a binding agreement on
the part of SAP AG or any of its subsidiaries to enter into any relationship,
unless otherwise expressly stated. </FONT></SPAN></P>
<DIV> </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>John White<BR><B>Sent:</B>
Wednesday, 20 June 2007 6:53 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Difference between Business object method and ABAP
class methodsin atask<BR></FONT><BR></DIV>
<DIV></DIV>
<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 style="COLOR: black" bgColor=white>
<TBODY>
<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></TBODY></TABLE></BODY></HTML>