<html><body bgcolor="#FFFFFF"><div>Rick,</div><div><br></div><div>The concept of 'passing' anything between BOR and ABAP OO is probably going to cause you a monumental headache. </div><div><br></div><div>Containers based on the SWCONT structure are just too far behind their newer ABAP_PARMBIND equivalents to understand the concept of an ABAP OO instance. </div><div><br></div><div>'TYPE REF TO data' simply did not exist back then. Just as 'TYPE BOXED' is going revolutionise the Data Dictionary (at long last!) and hasn't quite hit us yet in the current world. </div><div> </div><div>But you may have hit that iceberg already...</div><div><br></div><div>Mike GT<br><br>Sent from my iPhone</div><div><br>On 23 Feb 2011, at 13:38, "Sample, Rick" <<a href="mailto:Rick.Sample@graybar.com">Rick.Sample@graybar.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<div class="Section1">
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">Hi
Rina,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">You
will only get the display method link if you pass in an objects. Any object you
pass into a task with a display method will create the link. I only have my
ABAP object used in task tsxxxx, so I only see one. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">Did
I miss read this, or this what you referring to? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black">Rick<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Rina Spector<br>
<b>Sent:</b> Tuesday, February 22, 2011 9:58 PM<br>
<b>To:</b> SAP Workflow Users' Group<br>
<b>Subject:</b> Re: ABAP Objects - Percent of WF'ers using ABAP OO?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Dear Rick ,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Good for you if you are happy with your
craft .<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hopefully you had at least 2 display
methods to implement so no one asks why there
are 2 links that point to the same VA03.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I also do this mixture not so sure any one
except me will find where to look what ,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Best Regards <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rina spector <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA">On Tue, Feb 22, 2011 at 8:48 PM, Sample, Rick </span><span dir="LTR"></span><span dir="LTR"></span><span dir="LTR"><span dir="LTR"></span><span dir="LTR"></span><<a href="mailto:Rick.Sample@graybar.com"><a href="mailto:Rick.Sample@graybar.com">Rick.Sample@graybar.com</a></a>></span><span dir="RTL"></span><span dir="RTL"></span><span lang="AR-SA"><span dir="RTL"></span><span dir="RTL"></span> wrote:</span><span dir="LTR"><o:p></o:p></span></p>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA">All interested parties,<br>
<br>
Like I said, I am at the beginning of completing my first prod app in ABAP OO.
Low priority thing to test the waters for our company and expand our
knowledge. So I was poking a lot of people to get an idea of the best place to
start.<br>
Thanks ALL for input. Especially Mike, Mike, and Jocelyn.<br>
<br>
Yes, I am still waiting for my book "Practical Workflow for SAP 2nd
Edition". (Can't wait for my royalty checks for plugging the book!)<br>
<br>
At this point, I just kept my design as simple and light weight as possible. I
will expand on my (small) frame work / interfaces for all my known common
functions (best I can anyway) and refactor / evolve when and where
needed. It is a low priority project, not the never ending story, so I had to
take my best shot and go with what I know.<br>
<br>
Didn't touch the exits, type linkages, etc. to create events in ABAP OO, I just
caught the standard BOR BUS2032.CREATE / CHANGE and instantiate the object when
the flow starts. I already had that in place, so I know this works. Good enough
for now. I will need GOS so I can't get away from using BOR anyway.<br>
<br>
I have kicked off a Sales Order WF by using BOR events, using an ABAP OO class
as the core business code warehouse for this project. Simple functionality at
this point, but it fills the requirements.<br>
<br>
So Gavin, add (1) to that list not employed by SAP to use ABAP OO.<br>
<br>
Bottom line, did I 'need' ABAP OO for anything I did. Absolutely not. Just to
get me feet wet type experience and see what I can leverage from OO. It was
actually kinda fun. A lot of digging in the SWT* packages for some simple how
to code like get/set container, raise event, etc. Basic WF functionality but in
OO.<br>
<br>
Reference Jocelyn Dart "Why use ABAP OO with Workflow".<br>
Thanks Jocelyn. Excellent tutorial to make 'something' actually work.<br>
<br>
Rick Sample<br>
<br>
<br>
To quote an idiot:<br>
"There are known knowns; there are things we know we know.<br>
We also know there are known unknowns; that is to say, we know there are
some things we do not know.<br>
But there are also unknown unknowns - the ones we don't know we don't
know."<br>
- Former United States Secretary of Defense Donald Rumsfeld<br>
(It all makes sense... if you don't think about it.)<o:p></o:p></span></p>
<div>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA"><br>
<br>
<br>
<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:sap-wug-bounces@mit.edu"><a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></a><br>
> [mailto:<a href="mailto:sap-wug-bounces@mit.edu"><a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></a>]
On<br>
> Behalf Of Madgambler<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA">> Sent: Monday, February 21, 2011 4:22<br>
> PM<br>
> To: SAP Workflow Users' Group<br>
> Cc: SAP Workflow Users' Group<br>
> Subject: Re: ABAP Objects - Percent of<br>
> WF'ers using ABAP OO?<br>
><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA">> Rick,<br>
><br>
> So that post looks like it was written for<br>
> Netweaver 2004s. If SAP had seen<br>
> anything worthwhile in delivering that<br>
> promise I think it has long since<br>
> evaporated. Around about the same time<br>
> as they changed tack and poured effort<br>
> into Java stuff I would have thought.<br>
><br>
> Certainly when we upgraded to ECC 6<br>
> there was no mention at all of re-pointing<br>
> our extensive use of Workflow towards<br>
> ABAP OO. So between your post snippet<br>
> and the ECC 6 push either the money ran<br>
> out or the will or both.<br>
><br>
> On the brighter side Mike P tells me that<br>
> we should expect a new SE24-type editor<br>
> for Workflow Classes at some point soon<br>
> which would a step in the right direction at<br>
> least.<br>
><br>
> Although, I admit, I still miss the line editor<br>
> on the old R/2 days now and then and am<br>
> sometimes a little lost in the new multiple-<br>
> coloured collapsible section editor<br>
><br>
> Sent from my iPhone<br>
><br>
> On 21 Feb 2011, at 21:25, "Sample, Rick"<br>
> <<a href="mailto:Rick.Sample@graybar.com"><a href="mailto:Rick.Sample@graybar.com">Rick.Sample@graybar.com</a></a>>
wrote:<br>
><br>
> > Hi Mikes,<br>
> ><br>
> >> From all I have read, and that's quite a<br>
> bit. BOR was never intended<br>
> >> to be the model for object oriented<br>
> design. And indeed states that in<br>
> >> its own SAP Help files. "The BOR<br>
> object model will be integrated into<br>
> >> ABAP Objects in the next Release by<br>
> migrating the BOR object types to<br>
> >> the ABAP class library."<br>
> >><br>
> <a href="http://help.sap.com/saphelp_nw2004s/help" target="_blank"><a href="http://help.sap.com/saphelp_nw2004s/help">http://help.sap.com/saphelp_nw2004s/help</a></a><br>
> data/en/c3/225b5654f411d194a6<br>
> >> 0000e8353423/frameset.htm<br>
> > Sounds fairly straight forward to me. But<br>
> as of yet, not so integrated.<br>
> ><br>
> > My reading / translation, all standard<br>
> BORs will be rolled up into ABAP Objects,<br>
> ported over with something like<br>
> cl_BUS2032.<br>
> ><br>
> > Hate to sound like the kids in the back<br>
> seat, asking if we are there yet, but this is<br>
> exactly the answers (direction) I am<br>
> seeking. Where we going, when, how long<br>
> will it take to get there, will there be ports<br>
> (as stated in the help file), standards for<br>
> mixing the two, etc.<br>
> > I understand, some have confidentiality<br>
> clauses. (Just tell me. I<br>
> > promise, I won't tell anyone)<br>
> ><br>
> > Any recent official word from SAP on<br>
> this subject? If we know, we know. If we<br>
> are still winging it (SAP that is) and<br>
> checking the wind direction, that's cool<br>
> too. I understand, it's a BIG ship. But I am<br>
> sure there are several others that would<br>
> start if better direction from SAP.<br>
> ><br>
> > As far as BOR goes, anyone who will<br>
> work in our WF dept, MUST have BOR<br>
> experience at this point in time. That's not<br>
> going away any time soon because of all<br>
> the BOR code that we have developed.<br>
> And until I am 100% confident that I can<br>
> bang out something quick in ABAP<br>
> Objects, if a high priority comes down the<br>
> pipe line, it will most likely be written in<br>
> BOR.<br>
> ><br>
> > Rick<br>
> ><br>
> ><br>
> >> -----Original Message-----<br>
> >> From: <a href="mailto:sap-wug-bounces@mit.edu"><a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></a><br>
> >> [mailto:<a href="mailto:sap-wug-bounces@mit.edu"><a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a></a>]
On<br>
> >> Behalf Of Madgambler<br>
> >> Sent: Monday, February 21, 2011<br>
> 12:48 PM<br>
> >> To: SAP Workflow Users' Group<br>
> >> Cc: SAP Workflow Users' Group<br>
> >> Subject: Re: ABAP Objects - Percent<br>
> of WF'ers using ABAP OO?<br>
> >><br>
> >> Mike,<br>
> >><br>
> >> Interestingly that's where we disagree<br>
> most.<br>
> >><br>
> >> I don't believe it is in a client's interest<br>
> to ignore any future<br>
> >> adjustments of BOR functionality out of<br>
> hand and branch out with an<br>
> >> ABAP OO 'ported' version based on a<br>
> snapshot of the current standard<br>
> >> object.<br>
> >><br>
> ><br>
><br>
> __________________________________<br>
> _____________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu"><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap" target="_blank"><a href="http://mailman.mit.edu/mailman/listinfo/sap">http://mailman.mit.edu/mailman/listinfo/sap</a></a><br>
> -wug<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu"><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank"><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></a><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" dir="RTL" style="text-align:right;direction:rtl;unicode-bidi:
embed"><span lang="AR-SA"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>SAP-WUG mailing list</span><br><span><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a></span><br><span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></span><br></div></blockquote></body></html>