triggering a function module and not a workflow

[Srinivasan Ramanan]

Hi Susan,
If you do not want to execute the workflow with single step dialog or even 
with a single background step, it would be possible to achieve what you are 
expecting to happen with out the use of workflow.

your direction of thinking about user exit and FM is alos a good idea.

In a similar situation with our client we achieved execution of a report as 
soon as a delivery is saved.

The design is :
A report 'Z123456' is submitted after a raised event 'ZCONTORLXXXX'.

In our case the event also was defined by us, not an std SAP triggering 
event. The user exit triggers an event called 'ZCONTROLXXXX'.

BG Job is scheduled with as periodic job after an event .

Hope you could still progress in your direction
regards
Srinivasan


>From: Susan Keohan <keohan at ll.mit.edu>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: Re: triggering a function module and not a workflow
>Date: Tue, 13 Feb 2007 06:49:08 -0500
>
>I think that the visibility of how this function gets triggered far
>outweighs the steps necessary to start up Workflow.  But then again,
>this is a Workflow forum, and I don't see that as a big deal.
>
>I've been on the receiving end (so to speak) of trouble shooting
>production issues, and would much much rather have a reliable log to
>turn to (in addition to excellent docu, of course).  So all in all, I
>agree with Gavin and Henk.
>
>Besides, maybe your client will get a taste of WF, and want to do more
>stuff to improve business processes.  Then all that SWU3 stuff is
>already done!
>
>Gavin Mooney wrote:
> > Vali,
> >
> > Yes you could use a Receiver Function Module (not a receiver type
> > FM...) that would be executed when the event is raised. I personally
> > don't really like this approach because I think you lose visibility
> > (if the event trace isn't activated (i.e. in Production) then it might
> > be hard for someone to work out what triggered the FM.
> >
> > I would have suggested using a single step task and putting your FM
> > inside the task method, but if you don't want to use workflow at all
> > then maybe it's an option for you...
> >
> > Regards,
> > Gavin
> >
> > 2007/2/13, Vali Ivanov <vali.ivanov at gmail.com>:
> >> Yes, this was my first option also, but in that system, the client 
>don't
> >> have any workflows, and I didn't want to do any, with all the steps
> >> required.
> >>
> >> I think there is another way, maybe we 'receiver function', but I 
>didn't see
> >> how, yet
> >>
> >>
> >>
> >>   _____
> >>
> >> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
>Behalf Of
> >> Smit, Henk
> >> Sent: Tuesday, February 13, 2007 12:56 PM
> >> To: SAP Workflow Users' Group
> >> Subject: RE: triggering a function module and not a workflow
> >>
> >>
> >>
> >> Why not create a single step workflow (standard task TS...), which 
>calls a
> >> BOR method which calls your FM ?
> >>
> >>
> >>
> >> Seems simple enough and this way you use standard WF functionality.
> >>
> >>
> >>
> >> best regards,
> >>
> >> Henk Smit
> >>
> >>
> >>
> >>   _____
> >>
> >> Van: sap-wug-bounces at mit.edu namens Vali Ivanov
> >> Verzonden: di 13-2-2007 11:35
> >> Aan: sap-wug at mit.edu
> >> Onderwerp: triggering a function module and not a workflow
> >>
> >>
> >>
> >>
> >>
> >> Hello,
> >>
> >> I have a question about triggering a function module, or another 
>report,
> >> program,  when an event of a business object is triggered.
> >>
> >> Maybe this was discussed earlier but I couldn't find any information.
> >>
> >> The scope is to use the event of an business objects as an user exit 
>and to
> >> run a function module when this event occurs without putting all this 
>into a
> >> small workflow.
> >>
> >> Thanks.
> >>
> >>
> >>
> >> This e-mail and any attachment is for authorised use by the intended
> >> recipient(s) only. It may contain proprietary material, confidential
> >> information and/or be subject to legal privilege. It should not be 
>copied,
> >> disclosed to, retained or used by, any other party. If you are not an
> >> intended recipient then please promptly delete this e-mail and any
> >> attachment and all copies and inform the sender. Thank you.
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> >
>
>--
>Susan R. Keohan
>SAP Workflow Developer
>MIT Lincoln Laboratory
>244 Wood Street
>LI-200
>Lexington, MA. 02420
>781-981-3561
>keohan at ll.mit.edu
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug

_________________________________________________________________
Search for grocery stores. Find gratitude. Turn a simple search into 
something more. 
http://click4thecause.live.com/search/charity/default.aspx?source=hmemtagline_gratitude&FORM=WLMTAG