ABAP-OO Workflow for PO-release

Mike Pokraka wug at workflowconnections.com
Mon Apr 21 07:20:23 EDT 2008


On Fri, April 18, 2008 7:56 am, Kjetil Kilhavn wrote:
> This is interesting (well, anything from a SAP employee who has proven
OK I may not be a SAP Employee so take my input with a grain of salt..

> However, I have assumed that for existing BOR objects it would be easier to
> implement additional methods (and redefine methods) in a BOR object type
which would then be delegated to.
>
It's a little more work to create the class up front - there's no "Create
Subclass" button. But once that's in place I find it easier to add
additional methods. See my other post to Sherie.


> Would you recommend that even for a small change such as the additional
attribute I've added to USR01?
> Such a strategy would mean the workflow becomes a mixture of tasks using
BOR
> objects and class objects.
>
Yes, and yes. Actually in many cases I've done away with the BORs because
it's a 10 minute job to add the two or three BOR components I actually
need into my class. The icing on the cake is being able to bind
_WI_ACTUAL_AGENT via functional method straight into an instance of
ZCL_WF_USER.

> I see you recommend adding an attribute to the class to reference the
BOR
> object when needed. Would you recommend also adding a class object
reference
> as an attribute to a delegated BOR object type - or how would you
approach
> the need for crossing from one object type to the other.
Unfortunately it only works one way - BORs can't have class attributes.
Usually I end up working with both, which is not really a big issue.

> --
> Kjetil Kilhavn (+47 40220607)
> Blue Consulting AS (http://www.bluec.no/)
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>







More information about the SAP-WUG mailing list