<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>DIV {
MARGIN: 0px
}
</STYLE>
<META content="MSHTML 6.00.6000.17093" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=643475216-24022011><FONT face=Arial
color=#0000ff size=2>I hesitated to respond because though I am using ABAP OO
with Workflow, I'm no expert so I'm sure I'm not using it to it's full
advantage. But it's been great! Like Gretchen I now use ABAP OO for new
development and changes, but we still have a lot of BOR in place.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=643475216-24022011><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=643475216-24022011><FONT face=Arial
color=#0000ff size=2>Judy Alfano
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=643475216-24022011><FONT face=Arial
color=#0000ff size=2>MassMutual Financial Group</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=643475216-24022011><FONT face=Arial
color=#0000ff size=2>Springfield, MA</FONT></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>Gretchen
Roberts<BR><B>Sent:</B> Thursday, February 24, 2011 11:46 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: ABAP Objects - Percent of WF'ers
using ABAP OO? ( zip zilch nada ZERO people using ABAP OO with WF?
)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif">
<DIV></DIV>
<DIV>I use the OO exits! They are great! There is also a ton of
stuff you can accomplish in the binding when you call OO methods to populate
container values. So many background tasks can be
avoided!</DIV>
<DIV> </DIV>
<DIV>For new requests I almost always create classes instead of using
BOR objects. I do experience a small amount of guilt when
I re-invent the wheel--but it is a much better wheel. Mostly my
workflows are a combination of both--many tasks calling old BOR methods and many
calling OO methods. Too time consuming to go back and rewrite
<EM>everything </EM>but when I need to do generic work I will always use my new
generic OO methods.</DIV>
<DIV> </DIV>
<DIV>Gretchen Roberts</DIV>
<DIV>Working in Houston, TX</DIV>
<DIV>CP Chem</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif"><BR>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif"><FONT
face=Tahoma size=2>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> "Sample, Rick"
<Rick.Sample@graybar.com><BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B> SAP Workflow Users' Group
<sap-wug@mit.edu><BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B>
Thu, February 24, 2011 10:15:39 AM<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: ABAP Objects - Percent of
WF'ers using ABAP OO? ( zip zilch nada ZERO people using ABAP OO with WF?
)<BR></FONT><BR>Hey Wug'ers<BR><BR>Honestly, I really expected a few more
results on WF folks using ABAP OO. I see so much potential for adding it to the
skill sets. Even if you don't use full ABAP Objects, just using a simple Program
Exit class ( in a very simple class even ) has been useful for me. Program
Exits, you can catch internal Task events. Like, if someone Logically Deletes a
WF, without it, it is just done. With something like zcl_CompleteProcess hung
off the template, will still execute the code. Very useful for me.
<BR><BR>Humph! Interesting. <BR><BR>Buehler... Buehler... anyone see
Ferris Buehler?
<BR><BR>Rick<BR><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu"
ymailto="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></DIV></DIV></DIV>
<P><pre wrap>---------------------------------------------------------
This e-mail transmission may contain information that is
proprietary, privileged and/or confidential and is
intended exclusively for the person(s) to whom it is
addressed. Any use, copying, retention or disclosure by
any person other than the intended recipient or the
intended recipient's designees is strictly prohibited. If
you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and
delete all copies.
---------------------------------------------------------
</pre></P></BODY></HTML>