How to restrict workflow launches ?

[GOURLET Gilles]

Thanks a lot Jocelyn,=20
You got it : switch to display mode then switch to create and all =
active
events appear : R/3 is still full of surprise for me ...
If you want to follow up, I would be interested to know if these =
conditions
come in addition or in substitution to "Check Module Functions" that I =
may
define using SWETYPV.
 
Regards,
Gilles.
 
-----Message d'origine-----
De : Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Envoy=E9 : mercredi 5 novembre 2003 00:49
=C0 : SAP-WUG at MITVMA.MIT.EDU
Objet : Re: How to restrict workflow launches ?
 
 
Hi Gilles,
You need to activate your event linkage.
Then go to transaction SWB_COND.  It starts in display mode.  Use the
Display/Change button
to swap to Change mode.  Then press the Create button.
Then you can search for all active event linkages without start =
condition.
Selecting the
event linkage will then allow you to create a start condition for that =
event
linkage.
Use the "Technical Names On" option if you have difficulty finding your
event linkage.
 
And by the way folks - it's great to see everyone is well aware of =
start
conditions functionality now!
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
Sent: Wednesday,5 November 2003 4:24 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How to restrict workflow launches ?
 
 
Hi,
 
In display mode all start conditions are shown, and I guess you don't =
have a
start condition at the moment, so
nothing is shown. In change mode however all linkages without start
condition are shown!
 
Regards,
 
Fred Kouw
 
GOURLET Gilles wrote:
 
> Thanks all for your help.
> If I sum up :
> . Regarding the transaction SWB_COND : it doesn't display anything to =
me
> even if I widen all criterias (conditions =3D *, business objects =3D =
*,
events
> =3D *).
> Since workflows are fired when I create a new PM notification, I =
should
see
> in the SWB_COND transaction my PM notification objet and the event
> "created", don't you think so ?
> . Using the events : I don't see how to restrict the existing event =
to
> "Notificationtyp is (TQ80-QMTYP =3D 01)". Do you mean I should create =
a new
> event and put this condition into the code or something else ?
> . I can adapt the starting FM "QQWF_EVENT_PM_NOTIF_CREATED",
> . I can use check Check Function Modules.
>
> Gilles.
>
> -----Message d'origine-----
> De : Becker, Stephan [mailto:stephan_becker.ext at siemens.com]
> Envoyi : mardi 4 novembre 2003 17:16
> @ : SAP-WUG at MITVMA.MIT.EDU
> Objet : Re: How to restrict workflow launches ?
>
> Use start conditions via transaction SWB_COND
>
> -----Mensaje original-----
> De: Schmidinger, Heinz (Unaxis IT BZ)
[mailto:heinz.schmidinger at unaxis.com]
> Enviado el: 04 November 2003 16:40
> Para: SAP-WUG at MITVMA.MIT.EDU
> Asunto: AW: How to restrict workflow launches ?
>
> Hi Gilles,
>
> I have running such WF for SM e.g.
>
> You can use the Events (e.g. 'CREATE') from Object BUS2038. This =
Events
> should be fired only if Notificationtyp is (TQ80-QMTYP =3D 01).
>
> Additional you can do a detailed filtering using a adaption of f.m.
> 'QQWF_EVENT_PM_NOTIF_CREATED'. This f.m. is used by SAP-Standard for
> starting WS00200065.
> WS00200065 is a SAP-Standard-Example which you can activate in the
> Customizing of PM.
>
> Maybe it helps.
>
> regrads
>
> Heinz
>
> -----Urspr|ngliche Nachricht-----
> Von: GOURLET Gilles [mailto:gilles.gourlet at airbus.com]
> Gesendet am: Dienstag, 4. November 2003 16:13
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: How to restrict workflow launches ?
>
> Dear all,
> I need your help to find a way to avoid launching PM notifications
workflow
> whatever the type of the notification is.
> I mean I only want new workflows to be launched for certain types of
> notifications.
> eg: PM Notification - type M1, M2 and M3 -> Workflow ; other types -> =
No.
> Thanks in advance,
> Gilles.
>
> This mail has originated outside your organization,
> either from an external partner or the Global Internet.
> Keep this in mind if you answer this message.
>
>
________________________________________________________________________=
____
_____________
> 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 mail has originated outside your organization,
either from an external partner or the Global Internet.=20
Keep this in mind if you answer this message.