Event linkage to instance method (ABAP-OO workflow)

[Mike Pokraka]

Thanks for answering your own questions out here too, very useful :-) 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Florin Wach
Sent: 23 November 2009 13:04
To: sap-wug at mit.edu
Subject: Re: Event linkage to instance method (ABAP-OO workflow)

Hi again,

I've found out, that the Instance-handler interface is used for wait-steps
or completion-events for work items only.

So I have programmed a generic static ON_EVENT-method that calls the
instance ON_EVENT-methods.

Best wishes,
Florin

-------- Original-Nachricht --------
Datum: Wed, 18 Nov 2009 15:49:55 +0100
Von: "Florin Wach" <florin.wach at gmx.net>
An: sap-wug at mit.edu
Betreff: Event linkage to instance method (ABAP-OO workflow)

Hello wuggies,

I'd like to link an event to a method call instead of a function module
(creating a workflow instance or something else).

I have found out, that if you implemented the interface
BI_EVENT_HANDLER_STATIC there's a method ON_EVENT coming up, basically
offering the parameters of the receiver function module but as static
method's importing paramater.

This is already somewhat workable.

However I also found the interface BI_EVENT_HANDLER that brings on instance
ON_EVENT method with it, and the database table SWFDEVTYP can be set to an
instance method: There's a field RECMETYP, which could be set to 'I' =
Generic Instance Method.
However, I haven't found a possibility to maintain that field with
transaction SWETYPV.

Has anyone of you used the event linkage to INSTANCE methods already?


With the very best wishes,
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

 

__________ Information from ESET Smart Security, version of virus signature
database 4749 (20100106) __________

The message was checked by ESET Smart Security.

http://www.eset.com