ABAP Objects vs. BOR to trigger event?

[Sample, Rick]

Mike P / Mike GT,

Forgot about the need for BOR to use GOS. 

The need for BOR to use GOS is a big one for determining my approach to this low priority prj. This is a re-write of one of our first WFs (newbie code, patches galore, etc.) so would like to look forward as far as possible, but grey areas to be figured out by SAP at a later time, I will just avoid for now. 

Replacement for BOR-GOS or coexistence of ABAP Objects-GOS? Time line? SAP plan? 

I need BOR to use GOS, so I think I will simply continue to use BOR for all the events, links, etc. and add in only new ABAP Object code where required. I can already just instantiate the object or as you stated below. 

This seems like the simplest approach to me. This sounds like what most will be required to do anyway unless a complete custom app with all its own events, etc. etc. Yes? 

Thanks,
Rick


> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On
> Behalf Of Mike Pokraka
> Sent: Wednesday, February 09, 2011
> 11:27 AM
> To: SAP Workflow Users' Group
> Subject: RE: ABAP Objects vs. BOR to
> trigger event?
> 
> Hi Rick,
> 
> Yes it is unfortunately necessary to have
> both in most cases. Sometimes I just have
> the BOR in the WF container purely so the
> workflow is visible from GOS. There are
> ways around that too but some things
> aren't always worth the effort.
> 
> A couple of ways around the instantiation:
> 1.  An event replicator. The BOR event
> receiver in SWETYPV is a method that
> looks at the BOR event and raises the clas
> event which starts the workflow. Not
> suitable for high-volume processes.
> 2. First prize is always to raise a class
> event in first place. If using change docs
> or the likes you're all set.
> 3. Create class instance in WF. This is
> what you have done, but far less
> performance overhead is via a static
> GET_INSTANCE functional method on the
> class: this can then be called in a
> conatiner operation step or even in a
> binding of the first step that needs it.
> 
> This is all explained in the second edition
> of the WF book. Author's prceeds go to
> charity so this is not advertising :-)
> 
> Cheers,
> Mike
> 
> 
> On Wed, February 9, 2011 4:39 pm,
> Sample, Rick wrote:
> > Note: I added a hack. I catch the BOR
> Created event, then in
> > background task, call a
> CREATE_INSTANCE method to populate
> the ABAP
> > objects instance, but this seems a little
> bit of a kludge way to do it.
> >
> >
> >
> >> -----Original Message-----
> >
> >> From: sap-wug-bounces at mit.edu
> >
> >> [mailto:sap-wug-bounces at mit.edu] On
> >
> >> Behalf Of Sample, Rick
> >
> >> Sent: Wednesday, February 09, 2011
> >
> >> 10:14 AM
> >
> >> To: SAP Workflow Users' Group
> >
> >> Subject: ABAP Objects vs BOR to
> trigger
> >
> >> event?
> >
> >>
> >
> >> Hi all,
> >
> >>
> >
> >> I am playing around with a WF using
> >
> >> ABAP Objects. I built the object, wf,
> some
> >
> >> tasks, and all seems to be going fine.
> >
> >>
> >
> >> The WF will be based on Sales
> >
> >> (BUS2032). I will obviously need to run
> >
> >> both BOR and ABAP objects to trigger
> the
> >
> >> CREATE, CHANGED, etc. events.
> When
> >
> >> BUS2032.CREATE triggers, how to I
> also
> >
> >> trigger ABAP Objects?
> >
> >>
> >
> >> What is the "Best practices" to run side
> by
> >
> >> side? I have several PDFs, but do not
> see
> >
> >> this addressed.
> >
> >>
> >
> >> Thanks,
> >
> >> Rick
> >
> >>
> >
> >>
> __________________________________
> >
> >> _____________
> >
> >> SAP-WUG mailing list
> >
> >> SAP-WUG at mit.edu
> >
> >>
> http://mailman.mit.edu/mailman/listinfo/sap
> >
> >> -wug
> >
> __________________________________
> _____________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> >
> http://mailman.mit.edu/mailman/listinfo/sap
> -wug
> >
> 
> 
> __________________________________
> _____________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap
> -wug