<br><font size=2 face="sans-serif">Jocelyn,</font>
<br>
<br><font size=2 face="sans-serif">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 size=2 face="sans-serif">Thanks for these blogs, I can't wait
reading the next ones.</font>
<br>
<br><font size=2 face="sans-serif">Warm greetings from austria and,</font>
<br>
<br><font size=2 face="sans-serif">kind regards,<br>
<br>
Christian Wallner<br>
IT Business Process Consultant Development<br>
</font>
<br><font size=2 face="sans-serif">Austria Technologie & Systemtechnik
AG <br>
http://www.ats.net</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Dart, Jocelyn"
<jocelyn.dart@sap.com></b> </font>
<br><font size=1 face="sans-serif">Gesendet von: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">21.06.2007 07:18</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Bitte antworten an<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">An</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Kopie</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Thema</font></div>
<td><font size=1 face="sans-serif">RE: Difference between Business object
method and ABAP classmethodsin atask</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></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>