ABAP Objects - Percent of WF'ers using ABAP OO?

[Mike Pokraka]

No worries about going long-winded, I am sure there are others on the
sidelines wondering whether they want to take the plunge.

BTW:
> 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!)

Author's royalties are donated to charity, so please do a good deed and
keep plugging the book. :)


On Wed, February 23, 2011 2:25 pm, Sample, Rick wrote:
> Whoa! I never stated anything about passing a BOR objects 'into' an ABAP
> OO objects or vs versa. Sorry if I did not communicate that well. Maybe it
> is just early and I misread what Rina was saying.
>
> I 'thought' she was referring to binding the WF-BOR (with its display
> method) to a Task. And then binding another ABAP OO (with its display
> method) to the same Task. Then, you would have to two links on the Task in
> the Description pane with two different Display method links.
> Like, in the default Display BOR method, open VA03. One Display method
> from the BOR and the other Display from the ABAP OO.
>
> I use one or the other in a task for this WF so I don't have that issue.
>
> I have used multiple BOR object in past for HR work, like the W-4 object,
> employee object, etc. All providing its own Display link and method call
> and find that handy so the intended user can review the data.
>
> p.s. for others:
> I apologize if I come across as a little 'off' or long winded. Just me
> trying to dig for answers and give credit where credit is due. And I
> always keep myself open and available in forum or sent directly to me. I
> just pass along any of my findings and hope it sheds light on a subject
> that someone may be able to use.
>
> Rick
>
>
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Madgambler
> Sent: Wednesday, February 23, 2011 7:53 AM
> To: SAP Workflow Users' Group
> Cc: SAP Workflow Users' Group
> Subject: Re: ABAP Objects - Percent of WF'ers using ABAP OO?
>
> Rick,
>
> The concept of 'passing' anything between BOR and ABAP OO is probably
> going to cause you a monumental headache.
>
> 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.
>
> '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.
>
> But you may have hit that iceberg already...
>
> Mike GT
>
> Sent from my iPhone
>
> On 23 Feb 2011, at 13:38, "Sample, Rick"
> <Rick.Sample at graybar.com<mailto:Rick.Sample at graybar.com>> wrote:
> Hi Rina,
>
> 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.
>
> Did I miss read this, or this what you referring to?
>
> Rick
>
>
>
> From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu>
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Rina Spector
> Sent: Tuesday, February 22, 2011 9:58 PM
> To: SAP Workflow Users' Group
> Subject: Re: ABAP Objects - Percent of WF'ers using ABAP OO?
>
> Dear Rick ,
> Good  for you if you are  happy  with your craft .
>
> 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.
> I  also  do this mixture  not so sure any one except me will find  where
> to  look  what ,
> Best Regards
> Rina spector
> On Tue, Feb 22, 2011 at 8:48 PM, Sample, Rick
> <Rick.Sample at graybar.com<mailto:Rick.Sample at graybar.com>> wrote:
> All interested parties,
>
> 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.
> Thanks ALL for input. Especially Mike, Mike, and Jocelyn.
>
> 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!)
>
> 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.
>
> 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.
>
> 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.
>
> So Gavin, add (1) to that list not employed by SAP to use ABAP OO.
>
> 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.
>
> Reference Jocelyn Dart "Why use ABAP OO with Workflow".
> Thanks Jocelyn. Excellent tutorial to make 'something' actually work.
>
> Rick Sample
>
>
> To quote an idiot:
> "There are known knowns; there are things we know we know.
>  We also know there are known unknowns; that is to say, we know there are
> some things we do not know.
>  But there are also unknown unknowns - the ones we don't know we don't
> know."
>  - Former United States Secretary of Defense Donald Rumsfeld
> (It all makes sense... if you don't think about it.)
>
>