<!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.3790.2885" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=555123209-20062007><FONT face=Arial
color=#0000ff size=2>Hi John,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007><FONT face=Arial
color=#0000ff size=2>Jocelyn has done a very useful series of blogs on this
subject, on SDN. You can find a list of all of her SDN blogs by clicking
the following link:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007> <FONT
face=Arial color=#0000ff size=2><A
href="https://weblogs.sdn.sap.com/pub/u/4075">https://weblogs.sdn.sap.com/pub/u/4075</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007><FONT face=Arial
color=#0000ff size=2>I hope this is what you were looking
for.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=555123209-20062007><FONT face=Arial
color=#0000ff size=2>Kind regards,<BR></FONT></SPAN><SPAN
class=555123209-20062007><FONT face=Arial color=#0000ff size=2><FONT
size=2> Sky</DIV>
<DIV dir=ltr align=left></FONT><B><FONT color=#000080>
<P><FONT size=1>Schuyler (Sky) Kimball</FONT></B></FONT><FONT size=1><FONT
face="Times New Roman" color=#000000> <BR></FONT><FONT color=#808080>Senior
Consultant</FONT></FONT><FONT face="Times New Roman" color=#000000 size=1>
<BR></FONT><FONT color=#808080><FONT size=1>SAP Consulting, Netweaver Practice
Unit<BR><B>SAP America, Inc.</B></FONT></FONT><FONT size=1><FONT
face="Times New Roman" color=#000000> <BR></FONT><FONT color=#808080>3 Van De
Graaff Drive, 4th Floor</FONT></FONT><FONT
face="Times New Roman"><BR></FONT><FONT color=#808080 size=1>Burlington, MA
01803-5148</FONT><FONT face="Times New Roman" color=#000000 size=1>
<BR><BR></FONT><A href="mailto:schuyler.kimball@sap.com"><U><FONT
size=1>schuyler<SPAN class=555123209-20062007> <dot> </SPAN>kimball<SPAN
class=555123209-20062007> <at> </SPAN>sap<SPAN class=555123209-20062007>
<dot> </SPAN>com</FONT></U></A><FONT face="Times New Roman" color=#000000
size=1> <BR></FONT><A href="http://www.sap.com/"><U><FONT color=#0000ff><FONT
size=1>http://www.sap.com</FONT></U></FONT></A></P></FONT></SPAN><BR></DIV>
<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 A
Haworth<BR><B>Sent:</B> Wednesday, June 20, 2007 4:45 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Difference between Business object
method and ABAP class methodsinatask<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Hi</FONT> <BR><BR><FONT
face=sans-serif size=2>Where/what should be my starting point for looking at the
OO workflow world as opposed to the historical BOR world.</FONT> <BR><BR><FONT
face=sans-serif size=2>Thanks</FONT> <BR><BR><FONT face=sans-serif
size=2>John<BR><BR><BR>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>This
is a PRIVATE message. If you are not the intended recipient, please delete
without copying and kindly advise us by e-mail of the mistake in delivery. NOTE:
Regardless of content, this e-mail shall not operate to bind CSC to any order or
other contract unless pursuant to explicit written agreement or government
initiative expressly permitting the use of e-mail for such
purpose.<BR>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Dart, Jocelyn"
<jocelyn.dart@sap.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/20/07 07:23 AM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: Difference between Business
object method and ABAP class methodsin
atask</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT face=Arial
color=blue size=2>Hi John, </FONT><BR><FONT size=3> </FONT> <BR><FONT
face=Arial color=blue size=2>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. </FONT><BR><FONT size=3> </FONT> <BR><FONT
face=Arial color=blue size=2>Otherwise stick with ABAP OO and link to the
existing BOR using an attribute of type SIBFLPORB. </FONT><BR><FONT
size=3> </FONT> <BR><FONT face=Arial color=blue size=2>Best of both worlds.
ABAP OO is soooooooooooooooo much easier to use for enhancements.
</FONT><BR><FONT size=3> </FONT>
<P><FONT face=Arial size=1>Regards,</FONT><FONT size=3> </FONT><FONT face=Arial
color=#000080 size=1><B><BR>Jocelyn Dart</B></FONT><FONT size=3> </FONT><FONT
face=Arial color=#808080 size=1><BR>Senior Consultant</FONT><FONT size=3>
</FONT><FONT face=Arial color=#808080 size=1><B><BR>SAP Australia Pty
Ltd.</B></FONT><FONT size=3> </FONT><FONT face=Arial color=#808080
size=1><BR>Level 1/168 Walker St.</FONT><FONT size=3> </FONT><FONT face=Arial
color=#808080 size=1><BR>North Sydney <BR>NSW, 2060</FONT><FONT size=3>
</FONT><FONT face=Arial color=#808080 size=1><BR>Australia</FONT><FONT size=3>
</FONT><FONT face=Arial color=#808080 size=1><BR>T +61 412 390
267</FONT><FONT size=3> </FONT><FONT face=Arial color=#808080 size=1><BR>M
+ 61 412 390 267</FONT><FONT size=3> </FONT><FONT face=Arial
color=#808080 size=1><BR>E jocelyn.dart@sap.com</FONT><FONT size=3>
</FONT><FONT face=Arial color=blue size=1><U><BR></U></FONT><A
href="http://www.sap.com/"><FONT face=Arial color=blue
size=1><U>http://www.sap.com</U></FONT></A><FONT size=3> </FONT>
<P><FONT face="Times New Roman" color=red 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>
<P><FONT face="Times New Roman" color=red 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>
<P><FONT face="Times New Roman" color=red 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>
<P><FONT size=3></FONT> <BR><BR>
<HR>
<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<B><BR>Sent:</B>
Wednesday, 20 June 2007 6:53 AM<B><BR>To:</B> SAP Workflow Users'
Group<B><BR>Subject:</B> RE: Difference between Business object method and ABAP
class methodsin atask</FONT><FONT size=3><BR></FONT><BR><FONT face=Arial
color=blue 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> <BR><FONT size=3> </FONT> <BR><FONT
size=3>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. </FONT><BR><FONT size=3> </FONT> <BR><FONT
face=Arial color=blue size=2>and,</FONT> <BR><FONT size=3><B>ABAP
CLASS</B><BR>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.<B><BR>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).</FONT>
<BR><FONT size=3> </FONT> <BR><BR>
<HR>
<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<B><BR>Sent:</B> Monday, June 18, 2007 1:41 PM<B><BR>To:</B>
sap-wug@mit.edu<B><BR>Subject:</B> Difference between Business object method and
ABAP class methods in atask</FONT><FONT size=3><BR></FONT><BR><FONT
face=sans-serif size=2>Hi,</FONT> <BR><FONT face=sans-serif size=2> </FONT>
<BR><FONT face=sans-serif size=2> 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...</FONT>
<BR><FONT face=sans-serif size=2> Thanks a lot for all ur support.</FONT>
<BR><FONT face=sans-serif size=2> </FONT> <BR><FONT face=sans-serif
size=2>Thanks</FONT> <BR><FONT face=sans-serif size=2>Albina</FONT>
<BR><BR><FONT size=3>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></FONT>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="100%" bgColor=white><FONT size=3><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.</FONT></TR></TBODY></TABLE><BR><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></BODY></HTML>