Fields 'Main program' in 'Event data' available in start condition?

Kouw, FA - SPLTX fa.kouw at td.klm.com
Fri Oct 24 11:17:30 EDT 2003


Thanks again for your (quick) reply!
 
>From tx SWEC it seems possible to specify a 'Event container FM' for access to the event container. This looks to me as a possible place to fill a container element (event parameter) with a value that I can test in the start condition. If this isn't possible than I'll follow your advise, which is a smart way to use standard SAP
functionality and add your own rules.
 
Regards,
 
Fred Kouw
 
Michael Pokraka wrote:
 
> Gotcha, and of course since a container is a variable table, it will not be visible in the condition editor.
> Another technique I've used is to write my own check function, which in turn calls the start conditions. Thus write a FM that has the same interface as SWB_CHECK_FB_START_COND_EVAL, checks the container, and calls SWB_CHECK_FB_START_COND_EVAL. This adds your check, and leaves any start condition functionality still in place.
> HTH
> Cheers
> Mike
>
> On Fri, Oct 24, 2003 at 03:43:33PM +0200, Kouw, FA - SPLTX wrote:
> > Hi Mike,
> >
> > I do raise the custom event myself by linking the event to the change document MATERIAL (on update). It's the first time I've
> > used this way of raising an event. Is it possible to fill an event parameter in the event container with a value? Is the 'event
> > container FM' meant for this?
> >
> > Regards,
> >
> > Fred Kouw
> >
> > Michael Pokraka wrote:
> >
> > > Hi Fred,
> > > Since you're obviously raising the event yourself, why not drop SY-REPID or SY-TCODE into the event container and check that.
> > > HTH
> > > Cheers
> > > Mike
> > >
> > > On Tue, Oct 21, 2003 at 03:34:35PM +0200, Kouw, FA - SPLTX wrote:
> > > > Hi,
> > > >
> > > > When I look at the event data of an event in the event trace (tx 'SWEL')
> > > > then I see a field with name 'Main program'. I need the value of this
> > > > field to test in a start condition if the workflow must be started for
> > > > the event raised. However, when looking at the data available in the
> > > > event container when displaying the start condition then I can't locate
> > > > this field. Is there someway to access this field for testing if my
> > > > workflow must be started?
> > > >
> > > > Why I want this? I have a custom event 'Z_Changed' linked to change
> > > > document 'MATERIAL' (when a material is changed using tx 'MM02' I want
> > > > to trigger my workflow). From the workflow materials related to the
> > > > changed material (grouped in the same FFF class) are changed in
> > > > background using tx 'MPND' (A&D specific). But when materials are
> > > > changed in background using tx 'MPND' then change documents of type
> > > > MATERIAL are created and this in turn starts a workflow for each of the
> > > > changed materials.... I need to check if the event was created by
> > > > program 'RMPNCOPY' attached to tx 'MPND' (which is displayed in the
> > > > event data of the event raised). It isn't sufficient to check if the
> > > > user who created the change document is or isn't WF-BATCH, because when
> > > > tx 'MPND' results in an error then a user is offered a work item in the
> > > > workflow which allows him/her to run tx 'MPND' in dialog (and if this
> > > > user changes the related materials I do not want the workflow to be
> > > > started for each of the changed materials). The transaction shown in the
> > > > change document MATERIAL is in all cases 'MM02'.
> > > >
> > > > Regards,
> > > >
> > > > Fred Kouw
> > > >
> > > >
> > > >
> > > > **********************************************************************
> > > > This e-mail and any attachment may contain confidential and privileged
> > > > material intended for the addressee only. If you are not the addressee, you
> > > > are notified that no part of the e-mail or any attachment may be disclosed,
> > > > copied or distributed, and that any other action related to this e-mail or
> > > > attachment is strictly prohibited, and may be unlawful. If you have received
> > > > this e-mail by error, please notify the sender immediately by return e-mail,
> > > > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> > > > subsidiaries and/or its employees shall not be liable for the incorrect or
> > > > incomplete transmission of this e-mail or any attachments, nor responsible
> > > > for any delay in receipt.
> > > > **********************************************************************
> > > >
> > > > _____________________________________________________________________________________________
> > > > This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> > > > For further information visit: http://www.veiliginternet.nl
> > > > _____________________________________________________________________________________________
> > >
> > > _________________________________________________________________________________________
> > > This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > > _____________________________________________________________________________________________
> >
> >
> > **********************************************************************
> > This e-mail and any attachment may contain confidential and privileged
> > material intended for the addressee only. If you are not the addressee, you
> > are notified that no part of the e-mail or any attachment may be disclosed,
> > copied or distributed, and that any other action related to this e-mail or
> > attachment is strictly prohibited, and may be unlawful. If you have received
> > this e-mail by error, please notify the sender immediately by return e-mail,
> > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> > subsidiaries and/or its employees shall not be liable for the incorrect or
> > incomplete transmission of this e-mail or any attachments, nor responsible
> > for any delay in receipt.
> > **********************************************************************
> >
> > _____________________________________________________________________________________________
> > This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> > _____________________________________________________________________________________________
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
 
 
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************
 
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________
 


More information about the SAP-WUG mailing list