ABAP-OO Workflow for PO-release

Wed Apr 16 10:35:37 EDT 2008

Hi again,

thanks for your feedback!

I thought of re-routing the event by a receiver function module to get the 
actual OO-event in place. I'll implement a generic one that'll cover that 
one. I just wanted to be sure, not to oversee a huge part about eventening & 
OO that had made this part of development obsolete.

Thanks again,
   Florin

----- Original Message ----- 
From: "Mike Pokraka" <wug at workflowconnections.com>
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Sent: Wednesday, April 16, 2008 3:21 PM
Subject: RE: ABAP-OO Workflow for PO-release

Dunno, I argued with polymorphism on a 620 system, but haven't really had
a need for it since.
All I can say is I'm having a nightmare working with BOR objects at the
moment. To be fair, this is partly due to some incredibly daft design by
SAP.

On Wed, April 16, 2008 12:51 pm, Alon Raskin wrote:
> Mike, any sign of polymorphism support in the WF builder yet?
> That was the main reason I steered away from OO in WF to this date.
> Without this I really donâ?Tt that there is so much to gain using OO in
> WF.
>
> Alon Raskin
> e: araskin at 3i-consulting.com
> p: +1 800 405 8605
> c: +1 207 409 4983
> f:  +1 806 403-4983
>
> Put SAP in your Pocket
> http://www.themobileworkplace.com
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Wednesday, April 16, 2008 6:47 AM
> To: SAP Workflow Users' Group
> Subject: Re: ABAP-OO Workflow for PO-release
>
> Hi Florin,
>
> Events are probably the least developed part of WF-OO and have a couple of
> areas where they are not 100% supported even in the latest greatest
> version.
>
> Nevertheless, this is completely irrelevant to your question and by no
> means a reason not to go down this route.
>
> Events are raised by the app. Having a new type of event doesn't mean the
> po will automatically raise it, it is still BUS2012 (and probably always
> will be). Think of it as having a new BO (e.g. PURCHORD) available to
> represent a PO. In other words there is no translation.
>
> It's annoying that you will still need to work with BOs for the eventing
> part, but there are two alternatives:
> * Trigger your WF from the event and instantiate a class object in the
> first step of your WF. This is quick and simple and works well.
> * Use a custom receiver to forward the event to your class.
>
> The second option is only really useful if you need to massage event info
> along the way. The problem is that e.g. ME23N's GOS will still look for
> BUS2012, so you will still need a BUS2012 in your WF as a container
> element.
>
> Stick with OO. I am currently on my first project in years where I'm
> forced to use BOR and it's not nice. I would violate posting guidelines if
> I said what I really think :-)
>
> Have fun,
> Mike
>
>
> On Wed, April 16, 2008 10:25 am, Florin Wach wrote:
>> Hi folk,
>>
>> I have the great opportunity to make a complete re-design of a workflow
>> implementation for the release procedure of purchase orders (that one
>> that
>> is about release-codes, etc.)
>>
>> I remember some previous postings that generally say that it's a very
>> nice
>> thing to make (more) use of ABAP-OO classes and such and read through
>> the
>> white paper "ABAP OO for SAP Business Workflow (including 6.40)" written
>> by Jocelyn Dart
>> <https://wiki.sdn.sap.com/wiki/display/HOME/2.+Design+and+Development#2.DesignandDevelopment-HowcanIuseABAPOOClassesinWorkflow%3F>
>> as found in the FAQ-Wiki within the SDN:
>> <https://wiki.sdn.sap.com/wiki/display/HOME/SAP+Business+Workflow+FAQ>
>>
>> I stumbled over something that says in chapter 6:
>> "Events of ABAP Classes are used in workflow in a similar way to BOR
>> events. When including an event of an ABAP Class in an event linkage,
>> the
>> following differences are noticeable:
>> Ã¢â,¬Â¢ The Ã¢â,¬Å"Object CategoryÃ¢â,¬Â must be set to Ã¢â,¬Å"ABAP
>> ClassÃ¢â,¬Â
>> Ã¢â,¬Â¢ The ABAP Class name is specified as the Ã¢â,¬Å"Object
>> TypeÃ¢â,¬Â
>> The event linkage acts as an event handler for the ABAP Class event.
>> To call events from programs use the class CL_SWF_EVT_EVENT.
>> ThereÃ¢â,¬â"¢s
>> also an interface for adding event parameters Ã¢â,¬â?o check the SAP
>> Library
>> help."
>>
>> Now I wonder, what the standard transactions are doing here, as the
>> events
>> for the Business Object BUS2012.ReleaseStepCreated (the most important
>> one) and BUS2012.Released are called within those transactions.
>>
>> I have rummaged through the classes via the reference of the interface
>> IF_WORKFLOW, but it seems that there could be something available for
>> purchase requisitions, but I didn't find anything about purchase orders.
>> Apparently I didn't find pretty much ABAP-OO classes at all.
>>
>> ===QUESTION===
>> Q: How are (SAP Standard) events from Business-Object-Types translated
>> into ABAP-OO events?  (Including any parameters passed, which then can
>> be
>> used in the event type linkage)
>>
>>
>> Best regards,
>>    Florin
>>
>> _______________________________________________
>> 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
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug 