ABAP Objects - Percent of WF'ers using ABAP OO? (Mike Pokraka)

[Andy Curtis]

 I have used ABAP Objects for almost everything I have done for the last 3
years or more.  So now, if I have to use a SAP Business Object it's only for
the initial triggering/conditions then when I have a template started, I
instantiate a Class to provide me with all the attributes/methods/events
that I want.

Started doing this as a self improvement, and it still gives me things to
think about, but I think it's clearer than SAP Business Objects.

The other benefit I see, at this client (large international commodity co),
where there are multiple projects going on around the world building their
own solutions for common processes on multiple development systems.  1
project delegates the SAP Business Object and then another project can't, so
they would need to include their methods/attributes/events in the first
projects delegation, then you get into all sorts of issues.  (Best to keep
separate) (or is that encapsulated)?





> ---------- Forwarded message ----------
> From: "Mike Pokraka" <wug at workflowconnections.com>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date: Mon, 21 Feb 2011 10:34:07 -0000 (GMT)
> Subject: Re: ABAP Objects - Percent of WF'ers using ABAP OO?
> Hi Rick,
>
> I know what you mean! Some theories I can offer based on my experiences:
>
> - Learning curve: Although OO requires far less specialist WF knowledge
> than BOR, there are still quite a few rules to work by.
>
> - Skillset: Many people learnt ABAP as a secondary skill to build better
> workflows. They have a handle on BOR and - no disrespect intended - the
> concept of relearning OO terrifies them. In some ways rightly so, BOR is a
> bit more forgiving for people just muddling through. OO on the other hand
> benefits from better programming skills, with the upshot of better quality
> solutions.
>
> - Installed base: Much SAP-delivered and custom-built functionality is
> already contained in BOR. People see it as a huge task to switch to OO,
> but this is really just a chicken and egg scenario because it's easy to
> port BOR to OO *if* you have good knowledge of WF-OO. (Hint: The Book v2.0
> will help with this!)
>
> For anyone sitting on the fence, I say: just do it! There's no need to
> make it a major undertaking, just tackle one thing at a time. As a rough
> guideline, anything new gets developed in OO and anything requiring
> changes is ported where practical.
>
> Have fun,
> Mike
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110221/38311a78/attachment.htm