<!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=610480308-22062007><FONT face=Arial
color=#0000ff size=2>Thanks Christian - glad you enjoyed
them!</FONT></SPAN></DIV>
<DIV> </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>Christian
Wallner<BR><B>Sent:</B> Thursday, 21 June 2007 5:44 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Antwort: RE: Difference between
Business object method and ABAPclassmethodsin atask<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Jocelyn,</FONT> <BR><BR><FONT
face=sans-serif size=2>Time to say thanks to you. After having read (and trying
your example zcl_plant ;)) your first blogs on sdn concerning abap oo and
workflow I'm even more enthusiastic about this topic than I was before
:-)</FONT> <BR><FONT face=sans-serif size=2>Thanks for these blogs, I can't wait
reading the next ones.</FONT> <BR><BR><FONT face=sans-serif size=2>Warm
greetings from austria and,</FONT> <BR><BR><FONT face=sans-serif size=2>kind
regards,<BR><BR>Christian Wallner<BR>IT Business Process Consultant
Development<BR></FONT><BR><FONT face=sans-serif size=2>Austria Technologie &
Systemtechnik AG <BR>http://www.ats.net</FONT> <BR><BR><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>Gesendet von: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>21.06.2007 07:18</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Bitte antworten
an<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>An</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>Kopie</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Thema</FONT></DIV>
<TD><FONT face=sans-serif size=1>RE: Difference between Business
object method and ABAP classmethodsin
atask</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><TT><FONT
size=2>Mike, <BR><BR>What are you on about...? More painful to create a class??
<BR><BR>Methinks someone needs a little practice in ABAP OO if you
think<BR>implementing an ABAP OO interface is more painful than learning
and<BR>using all those dense little workflow macros.... :-)<BR><BR>I think
ABAP OO is less painful all round... especially since once<BR>you've done one
class the IF_WORKFLOW methods <BR><BR>Also Sherie - appreciate your comments re
business analysts doing<BR>workflow, but I have seen some terrible
system-destroying things done by<BR>business analysts attempting coding so
apologies but it is really better<BR>to leave the coding to the programmers if
you can. If not, a basic ABAP<BR>OO course or following the blogs on SDN
should get you going in no time.<BR>You could also get a programmer to do the
first class as a template or<BR>even provide a root class that does the hard
work for you. <BR><BR><BR>Regards,<BR>Jocelyn Dart<BR>Senior
Consultant<BR>SAP Australia Pty Ltd.<BR>Level 1/168 Walker St.<BR>North Sydney
<BR>NSW, 2060<BR>Australia<BR>T +61 412 390 267<BR>M + 61 412 390
267<BR>E jocelyn.dart@sap.com<BR>http://www.sap.com<BR><BR>The
information contained in or attached to this electronic transmission<BR>is
confidential and may be legally privileged. It is intended only for<BR>the
person or entity to which it is addressed. If you are not the<BR>intended
recipient, you are hereby notified that any distribution,<BR>copying, review,
retransmission, dissemination or other use of this<BR>electronic transmission or
the information contained in it is strictly<BR>prohibited. If you have received
this electronic transmission in error,<BR>please immediately contact the sender
to arrange for the return of the<BR>original documents. <BR>Electronic
transmission cannot be guaranteed to be secure and<BR>accordingly, the sender
does not accept liability for any such data<BR>corruption, interception,
unauthorized amendment, viruses, delays or the<BR>consequences thereof.<BR>Any
views expressed in this electronic transmission are those of the<BR>individual
sender, except where the message states otherwise and the<BR>sender is
authorized to state them to be the views of SAP AG or any of<BR>its
subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>officers and
employees make no representation nor accept any liability<BR>for the accuracy or
completeness of the views or information contained<BR>herein. Please be aware
that the furnishing of any pricing information/<BR>business proposal herein is
indicative only, is subject to change and<BR>shall not be construed as an offer
or as constituting a binding<BR>agreement on the part of SAP AG or any of its
subsidiaries to enter into<BR>any relationship, unless otherwise expressly
stated. <BR><BR><BR>-----Original Message-----<BR>From: sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] On Behalf<BR>Of Mike Pokraka<BR>Sent: Thursday,
21 June 2007 2:18 AM<BR>To: SAP Workflow Users' Group<BR>Subject: RE: Difference
between Business object method and ABAP<BR>classmethodsin
atask<BR><BR>Sherie,<BR><BR>Note Jocelyn's little qualifier there: "...for
enhancements". :-)<BR><BR>Creating a class is more painful compared to BOR, but
once it's working<BR>and you need to modify/add stuff it very quickly becomes
worthwhile. A<BR>bonus (especially for non-programmers) is that you can then go
to any<BR>abap<BR>developer and ask them to add "a method that rejects item x in
the sales<BR>order" to your class - without having to explain a single thing
about<BR>workflow.<BR><BR>Both of the above have already come in handy in my own
projects and<BR>saved<BR>a lot of time.<BR><BR>Oh, and it's also fun; and
pleasant to work in a decent editor that has<BR>moved on from the 90's
:-)<BR>Cheers,<BR>Mike<BR><BR>On Wed, June 20, 2007 4:17 pm, Munday,Sherie J.
wrote:<BR>> Jocelyn,<BR>> ABAP OO may be better for programmers, but
remember there are many<BR>> workflow developers (like myself) who are Not
programmers and thus the<BR>> BOR is simpler for us.<BR>> Cheers,<BR>>
Sherie<BR>><BR>> ________________________________<BR>><BR>> From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<BR>Behalf<BR>> Of
Dart, Jocelyn<BR>> Sent: Wednesday, June 20, 2007 2:24 AM<BR>> To: SAP
Workflow Users' Group<BR>> Subject: RE: Difference between Business object
method and ABAP<BR>> classmethodsin atask<BR>><BR>><BR>> Hi
John,<BR>><BR>> Actually having worked with both ABAP OO for Workflow and
BOR my<BR>current<BR>> opinion is - only use BOR for eventing if you are
using - a standard<BR>> workflow as-is or an event technique that doesn't
support OO - like<BR>> status management events.<BR>><BR>> Otherwise
stick with ABAP OO and link to the existing BOR using an<BR>> attribute of
type SIBFLPORB.<BR>><BR>> Best of both worlds. ABAP OO is
soooooooooooooooo much easier to use<BR>> for
enhancements.<BR>><BR>><BR>> Regards,<BR>> Jocelyn Dart<BR>>
Senior Consultant<BR>> SAP Australia Pty Ltd.<BR>> Level 1/168 Walker
St.<BR>> North Sydney<BR>> NSW, 2060<BR>> Australia<BR>> T
+61 412 390 267<BR>> M + 61 412 390 267<BR>> E
jocelyn.dart@sap.com<BR>> http://www.sap.com
<http://www.sap.com/><BR>><BR>> The information contained in or
attached to this electronic<BR>transmission<BR>> is confidential and may be
legally privileged. It is intended only for<BR>> the person or entity to
which it is addressed. If you are not the<BR>> intended recipient, you are
hereby notified that any distribution,<BR>> copying, review, retransmission,
dissemination or other use of this<BR>> electronic transmission or the
information contained in it is strictly<BR>> prohibited. If you have received
this electronic transmission in<BR>error,<BR>> please immediately contact the
sender to arrange for the return of the<BR>> original
documents.<BR>><BR>> Electronic transmission cannot be guaranteed to be
secure and<BR>> accordingly, the sender does not accept liability for any
such data<BR>> corruption, interception, unauthorized amendment, viruses,
delays or<BR>the<BR>> consequences thereof.<BR>><BR>> Any views
expressed in this electronic transmission are those of the<BR>> individual
sender, except where the message states otherwise and the<BR>> sender is
authorized to state them to be the views of SAP AG or any of<BR>> its
subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>> officers
and employees make no representation nor accept any liability<BR>> for the
accuracy or completeness of the views or information contained<BR>> herein.
Please be aware that the furnishing of any pricing<BR>information/<BR>>
business proposal herein is indicative only, is subject to change and<BR>>
shall not be construed as an offer or as constituting a binding<BR>>
agreement on the part of SAP AG or any of its subsidiaries to
enter<BR>into<BR>> any relationship, unless otherwise expressly
stated.<BR>><BR>><BR>><BR>>
________________________________<BR>><BR>> From: sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] On<BR>Behalf<BR>> Of John White<BR>>
Sent: Wednesday, 20 June 2007 6:53 AM<BR>> To: SAP Workflow Users'
Group<BR>> Subject: RE: Difference between Business object method and ABAP
class<BR>> methodsin atask<BR>><BR>><BR>> I don't know the answer,
but here is what I found on SDN. My<BR>experience<BR>> has only been with BOR
object, creating new, and extending existing<BR>> ones. Hope this
helps!<BR>><BR>> BOR objects is the category that have been around for a
long time,<BR>while<BR>> CL is a (relatively) new possibility. You should use
whatever is more<BR>> practical in each case. For instance, if you are
working with<BR>employees<BR>> and everything you need is in BOR object
BUS1065 it makes sense to use<BR>> that BOR object. If you find a class that
has everything you need it<BR>> makes (even more) sense to use
that.<BR>><BR>> If you have to create a completely new object type you
should try to<BR>> create a class instead of a new BOR object. If you simply
need a<BR>little<BR>> bit of additional functionality or a new virtual
attribute, my<BR>> recommendation would be to extend the object type that
exists instead<BR>of<BR>> trying to create a class that extends a BOR
object.<BR>><BR>> and,<BR>> ABAP CLASS<BR>> Template for objects in
ABAP Objects. Defined using CLASS - ENDCLASS<BR>> either globally in a class
pool or locally in another ABAP program.<BR>The<BR>> definition of a class is
made up of a declaration section for the<BR>> declaration of theclass
components and animplementation section for<BR>the<BR>> implementation of the
methods.<BR>> BOR-OBJECT TYPES<BR>> mySAP Technology service and directory
of all object types (business<BR>> object types, organization object types
and technical object types) in<BR>> hierarchical order.<BR>> The object
types are each assigned to a packet (and thus indirectly<BR>also<BR>> 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<BR>> indirectly also to an application
component).<BR>><BR>><BR>>
________________________________<BR>><BR>> From: sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] On<BR>Behalf<BR>> Of Albina Fernando<BR>>
Sent: Monday, June 18, 2007 1:41 PM<BR>> To: sap-wug@mit.edu<BR>> Subject:
Difference between Business object method and ABAP class<BR>> methods in
atask<BR>><BR>><BR>> Hi,<BR>><BR>> Can anyone tell me the
difference between using Business Object<BR>method<BR>> and Class methods in
the tasks of the Workflow. For eg. When creating<BR>a<BR>> task we have 2
options. Either Assign a Business Object method or a<BR>ABAP<BR>> Object
class method. So I need to know the difference between the two.<BR>> And also
the advantages of using the two...<BR>> Thanks a lot for all ur
support.<BR>><BR>> Thanks<BR>> Albina<BR>><BR>><BR>> This
email may contain confidential or privileged information for the<BR>>
intended recipient(s). If you are not the intended recipient,
please<BR>do<BR>> not use or disseminate the information, notify the sender
and delete<BR>it<BR>> from your system. Thanks<BR>><BR>>
______________________________________________________________________<BR>><BR>><BR>><BR>><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>><BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>><BR><BR><BR>-- <BR>Mike
Pokraka<BR>Senior Consultant<BR>Workflow Connections<BR>Mobile: +44(0)7786
910855<BR><BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></FONT></TT><BR></BODY></HTML>