<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I have tried identifying and deleting
redundant workflow instances using a check function module but found it
unreliable - as pointed-out in a previous related post the workflows are
all created in the same LUW. I actually solved the problem by using
the FM </font><font size=2 color=#000080 face="Arial">SAP_WAPI_WORKITEMS_TO_OBJECT</font><font size=2 face="sans-serif">
as an initial step in the workflow template to identify duplicate instances
and then delete them (again described in an earlier post) and it worked
ok, although the overhead is that unecessary instances are created. If
you have control over the raising of the event then the terminating event
solution suggested seems promising.</font>
<br>
<br><font size=2 face="sans-serif">Karl Nietz<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Holt, Pamela F"
<pholt@ncdot.gov></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">22/05/2009 07:54 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"'SAP Workflow Users' Group'"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">RE: Triggering Events for HR</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2 color=blue face="Arial">I have two solutions. </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">First solution:</font>
<br><font size=2 color=blue face="Arial">1. Using a "fork" step,
put a "wait for terminating event" in your workflow (if you don't
already have one) that starts where the workflow starts and ends where
the workflow ends.</font>
<br><font size=2 color=blue face="Arial">2. In your program, raise the
terminating event right before you raise your triggering event. This
will terminate the workflow that is running. Follow the terminating event
with a COMMIT WORK AND WAIT, so that the workflow you are about to start
doesn't get terminated by mistake.</font>
<br><font size=2 color=blue face="Arial">3. Raise your triggering event.</font>
<br><font size=3> </font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Second solution:</font>
<br><font size=2 color=blue face="Arial">If the workflow doesn't already
have a check function module, create one. Insert the following code into
the check function module. This will terminate the workflow that
is already running in the check function module, before the workflow actually
starts.</font>
<br><font size=3> </font>
<br><font size=1 face="Arial monospaced for SAP"> DATA: t_sww_contob
TYPE TABLE OF sww_contob WITH HEADER LINE. </font>
<br><font size=1 face="Arial monospaced for SAP"> DATA: xswwwihead
TYPE TABLE OF swwwihead WITH HEADER LINE.</font>
<br><font size=1 face="Arial monospaced for SAP"> DATA: icount
TYPE i.</font>
<br><font size=1 color=blue face="Arial monospaced for SAP"> </font>
<br><font size=1 face="Arial monospaced for SAP"> CLEAR: t_sww_contob.
"look
for an active workflow</font>
<br><font size=1 face="Arial monospaced for SAP"> REFRESH: t_sww_contob.</font>
<br><font size=1 face="Arial monospaced for SAP"> </font>
<br><font size=1 face="Arial monospaced for SAP"> SELECT * FROM
sww_contob</font>
<br><font size=1 face="Arial monospaced for SAP">
INTO TABLE t_sww_contob</font>
<br><font size=1 face="Arial monospaced for SAP">
WHERE objtype = '<business_object_name>'</font>
<br><font size=1 face="Arial monospaced for SAP">
AND objkey = objkey</font>
<br><font size=1 face="Arial monospaced for SAP">
AND element = '<business_object_name>’.</font>
<br><font size=1 face="Arial monospaced for SAP"> </font>
<br><font size=1 face="Arial monospaced for SAP"> IF sy-subrc = 0.</font>
<br><font size=1 face="Arial monospaced for SAP"> DESCRIBE
TABLE t_sww_contob LINES icount.</font>
<br><font size=1 face="Arial monospaced for SAP"> IF icount
GT 0.</font>
<br><font size=1 face="Arial monospaced for SAP"> LOOP
AT t_sww_contob.</font>
<br><font size=1 face="Arial monospaced for SAP">
SELECT SINGLE * FROM swwwihead</font>
<br><font size=1 face="Arial monospaced for SAP">
INTO xswwwihead</font>
<br><font size=1 face="Arial monospaced for SAP">
WHERE wi_id = t_sww_contob-wi_id.</font>
<br><font size=1 face="Arial monospaced for SAP"> </font>
<br><font size=1 face="Arial monospaced for SAP">
IF sy-subrc = 0.
"an active workflow is found</font>
<br><font size=1 face="Arial monospaced for SAP">
IF xswwwihead-wi_stat = 'READY' OR</font>
<br><font size=1 face="Arial monospaced for SAP">
xswwwihead-wi_stat = 'WAITING' OR</font>
<br><font size=1 face="Arial monospaced for SAP">
xswwwihead-wi_stat = 'SELECTED' OR</font>
<br><font size=1 face="Arial monospaced for SAP">
xswwwihead-wi_stat = 'STARTED'.</font>
<br><font size=1 face="Arial monospaced for SAP">
RAISE <exception>.</font>
<br><font size=1 face="Arial monospaced for SAP">
ENDIF.</font>
<br><font size=1 face="Arial monospaced for SAP">
ENDIF.</font>
<br><font size=1 face="Arial monospaced for SAP"> </font>
<br><font size=1 face="Arial monospaced for SAP"> ENDLOOP.</font>
<br><font size=1 face="Arial monospaced for SAP"> ENDIF.</font>
<br><font size=1 face="Arial monospaced for SAP"> ENDIF.</font>
<p><font size=3> </font>
<br><font size=2 color=blue face="Arial">The difference between the two
solutions is that the first solution will always keep the last workflow
that was started, while the second solution keeps the first one. But they
both terminate the workflow before it actually starts executing.</font>
<br><font size=3> </font>
<br><font size=2 color=blue face="Arial">Regards,</font>
<br><font size=2 color=blue face="Arial">Pam Holt</font>
<br><font size=2 color=blue face="Arial">NCDOT</font>
<br>
<br>
<hr><font size=2 face="Tahoma"><b>From:</b> sap-wug-bounces@mit.edu [</font><a href="mailto:sap-wug-bounces@mit.edu"><font size=2 face="Tahoma">mailto:sap-wug-bounces@mit.edu</font></a><font size=2 face="Tahoma">]
<b>On Behalf Of </b>lynne.allen@kodak.com<b><br>
Sent:</b> Thursday, May 21, 2009 11:54 AM<b><br>
To:</b> sap-wug@mit.edu<b><br>
Subject:</b> Triggering Events for HR</font><font size=3><br>
</font>
<br><font size=2 face="sans-serif"><br>
This is a very basic question....</font><font size=3> </font><font size=2 face="sans-serif"><br>
When creating a recurring payment in HR, an SAP event of
CREATED (object recurrpay) is raised for each different wage type
used for an employee. <br>
For instance, if there are 3 wage types, 3 events are raised
for the SAME employee. After the creation of the payment and the
save key is hit the event kicks off, so for each payment for the same employee
we are getting 3 events. We do not want to start the WF 3x.</font><font size=3>
</font><font size=2 face="sans-serif"><br>
We want to start a workflow ONE time, as long as one payment exists start
the workflow, from there it does not matter how many payments are entered.
Any thoughts on how this can be done without started the workflow
for each time?</font><font size=3> <br>
<br>
</font><font size=2 face="sans-serif"><br>
</font>
<p><font size=1 color=#000080 face="Arial"><b>Lynne M. Allen</b></font><font size=1 face="Arial">
| ERP Workflow Development | Worldwide Information Systems (WWIS) | <br>
Eastman Kodak Company | 343 State Street | Rochester, NY 14650-1221 | </font><font size=3 color=blue><u><br>
</u></font><a href=mailto:lynne.allen@kodak.com><font size=1 color=blue face="Arial"><u>lynne.allen@kodak.com</u></font></a><font size=1 face="Arial">
| 585-724-3556 Office | </font><font size=3 color=blue><u><br>
</u></font><a href=http://www.kodak.com/><font size=1 color=blue face="Arial"><u>www.kodak.com</u></font></a><font size=1 face="Arial">
</font><font size=3><br>
</font><img src=cid:_1_07F1BDF007F1B584000A97E4CA2575BE>
<p><font size=3><br>
</font>
<hr><font size=1 color=#808080 face="Arial">Email correspondence to and
from this sender is subject to the N.C. Public Records Law and may be disclosed
to third parties.</font><tt><font size=2>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<p>