<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">Thanks lot for All your information!
</font>
<br>
<br><font size=2 face="sans-serif">I'm new to workflow, I'm not sure about
using fork steps please explain me How to implement in my existing workflow
as given below.</font>
<br>
<br><font size=2 face="sans-serif">If possible could please send me step
by step process for this activity.</font>
<br>
<br><img src=cid:_1_07500544074FF5940033E478652574BF>
<br>
<br><font size=2 face="sans-serif">Regards<br>
Muralitharan C<br>
Tata Consultancy Services<br>
Mailto: muralitharan.c@tcs.com<br>
Website: </font><a href=http://www.tcs.com/><font size=2 face="sans-serif">http://www.tcs.com</font></a><font size=2 face="sans-serif"><br>
____________________________________________<br>
Experience certainty. IT Services<br>
Business Solutions<br>
Outsourcing<br>
____________________________________________</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Florin Wach"
<florin.wach@gmx.net></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">09/09/2008 02:26 PM</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: Re: Deleting work item</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>addendum:<br>
<br>
plus, you can use under Basic-Data-->Workflow dependent settings-->Events
the<br>
BUS2105 / AllReleaseReset / 1 Cancel Workflow entry (as stated
by Aghrip in the SDN Forum Thread)<br>
<br>
<br>
<br>
<br>
-------- Original-Nachricht --------<br>
Datum: Tue, 09 Sep 2008 10:21:18 +0200<br>
Von: "Florin Wach" <florin.wach@gmx.net><br>
An: "SAP Workflow Users\' Group" <sap-wug@mit.edu><br>
Betreff: Re: Deleting work item<br>
<br>
Hello,<br>
<br>
please check WS20000077 Node #4 "Overall release of requisition",
referring to TS20000159 BUS2105.SingleRelease and terminating events:<br>
REJECTED<br>
RELEASED<br>
RESET<br>
SIGNIFICANTLYCHANGED<br>
<br>
As I can see you're probably using a general decision task to approver/reject
the purchase order? If so, I'd advice to use (a copy of) the standard task
TS20000159 and it's terminating events.<br>
<br>
Your event .Changed is probably triggered to often, so I'd recommend to
use the .ReleaseStepCreated event only to start the workflow (again).<br>
<br>
With your workflow pattern:<br>
You create a new parallel step right above the very first activity, before
doing any other thing. The parallel execution is to be defined as a "1
out of 2", so only one thread needs to end. On one side of the parallel
step you'll cut'n'paste all the steps that you have, and on the other side
you'll have your terminating event listener.<br>
<br>
<br>
So long & take care,<br>
Florin<br>
<br>
<br>
<br>
<br>
<br>
-------- Original-Nachricht --------<br>
> Datum: Tue, 9 Sep 2008 13:18:48 +0530<br>
> Von: muralitharan.c@tcs.com<br>
> An: "SAP Workflow Users\' Group" <sap-wug@mit.edu><br>
> CC: "SAP Workflow Users\' Group" <sap-wug@mit.edu>,
sap-wug-bounces@mit.edu<br>
> Betreff: Re: Deleting work item<br>
<br>
> Hi,<br>
> <br>
> I have modified PR Me52n and checked through swels and swel shows
<br>
> "Significant change" event is not triggered as shown.<br>
> <br>
> <br>
> But through parallel step where do we implement this parallel process
in <br>
> my workflow,as given below<br>
> <br>
> please suggest me and give me details if possible.<br>
> <br>
> If you have other difficulties here, because you're using your own
custom <br>
> workflow pattern, I'd advice to create a new event BUS2105.AllReleaseReset<br>
> and create this through the change documents BANF, restriction field:
<br>
> EBAN-FRGZU_OLD <> ' ' and EBAN_FRGZU_NEW = ' ' and
use this event to <br>
> terminate the complete existing workflow by a parallel step with an
<br>
> event-item listening to this particular event.<br>
> <br>
> This is my workflow steps,<br>
> <br>
> <br>
> Muralitharan C<br>
> Tata Consultancy Services<br>
> Mailto: muralitharan.c@tcs.com<br>
> Website: </font></tt><a href=http://www.tcs.com/><tt><font size=2>http://www.tcs.com</font></tt></a><tt><font size=2><br>
> ____________________________________________<br>
> Experience certainty. IT Services<br>
>
Business Solutions<br>
>
Outsourcing<br>
> ____________________________________________<br>
> <br>
> <br>
> <br>
> "Florin Wach" <florin.wach@gmx.net> <br>
> Sent by: sap-wug-bounces@mit.edu<br>
> 09/09/2008 12:38 PM<br>
> Please respond to<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> <br>
> <br>
> To<br>
> "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> cc<br>
> <br>
> Subject<br>
> Re: Deleting work item<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Hi,<br>
> <br>
> The SAP Standard will raise the event .SignificantlyChanged for obsolete
<br>
> work items. You'll need to correct and check your terminating events.<br>
> There can also be release dependent difference (especially on systems
<br>
> before 4.70), so please check also your event log (activated for BUS2105).<br>
> <br>
> If you have other difficulties here, because you're using your own
custom <br>
> workflow pattern, I'd advice to create a new event BUS2105.AllReleaseReset<br>
> and create this through the change documents BANF, restriction field:
<br>
> EBAN-FRGZU_OLD <> ' ' and EBAN_FRGZU_NEW = ' ' and
use this event to <br>
> terminate the complete existing workflow by a parallel step with an
<br>
> event-item listening to this particular event.<br>
> <br>
> The new workflow instance will be started by the <br>
> BUS2105.ReleaseStepCreated as usual.<br>
> <br>
> Best wishes,<br>
> Florin<br>
> <br>
> -------- Original-Nachricht --------<br>
> > Datum: Tue, 9 Sep 2008 12:14:07 +0530<br>
> > Von: muralitharan.c@tcs.com<br>
> > An: "SAP Workflow Users\' Group" <sap-wug@mit.edu><br>
> > Betreff: Deleting work item<br>
> <br>
> > Hi Friends,<br>
> > <br>
> > I'm having a issue in purchase requisition(PR) workflow, actually
when <br>
> PR <br>
> > is created then work item is generated in SAP inbox to approver(A)
and <br>
> > approved then work item will be send to second level approver
(B) then <br>
> > work item lies in second approver(B) level in between this time
PR <br>
> > creator(Intial Stage) modify the PR with the value then new release
<br>
> > strategy will be generated and Once again from first level the
process <br>
> > will be taken place then work item go to first approver
A and approved <br>
> > then go to second level B here already existing work item for
this PR <br>
> will<br>
> > be there as well generated one so dual work item is lying.<br>
> > <br>
> > Now I need to delete this work item from sap in-box in second
level B <br>
> > approver whether it's possible or not How come handle this situation?<br>
> > <br>
> > Please provide me solution for this scenario.<br>
> > <br>
> > Regards,<br>
> > <br>
> > Muralitharan C<br>
> > Tata Consultancy Services<br>
> > Mailto: muralitharan.c@tcs.com<br>
> > Website: </font></tt><a href=http://www.tcs.com/><tt><font size=2>http://www.tcs.com</font></tt></a><tt><font size=2><br>
> > ____________________________________________<br>
> > Experience certainty. IT Services<br>
> >
Business Solutions<br>
> >
Outsourcing<br>
> > ____________________________________________<br>
> > =====-----=====-----=====<br>
> > Notice: The information contained in this e-mail<br>
> > message and/or attachments to it may contain <br>
> > confidential or privileged information. If you are <br>
> > not the intended recipient, any dissemination, use, <br>
> > review, distribution, printing or copying of the <br>
> > information contained in this e-mail message <br>
> > and/or attachments to it are strictly prohibited. If <br>
> > you have received this communication in error, <br>
> > please notify us by reply e-mail or telephone and <br>
> > immediately and permanently delete the message <br>
> > and any attachments. Thank you<br>
> > <br>
> > <br>
> _______________________________________________<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>
> <br>
> ForwardSourceID:NT00007FCE <br>
> =====-----=====-----=====<br>
> Notice: The information contained in this e-mail<br>
> message and/or attachments to it may contain <br>
> confidential or privileged information. If you are <br>
> not the intended recipient, any dissemination, use, <br>
> review, distribution, printing or copying of the <br>
> information contained in this e-mail message <br>
> and/or attachments to it are strictly prohibited. If <br>
> you have received this communication in error, <br>
> please notify us by reply e-mail or telephone and <br>
> immediately and permanently delete the message <br>
> and any attachments. Thank you<br>
> <br>
> <br>
_______________________________________________<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>
_______________________________________________<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>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT00007FE6
</font>
<br><pre>=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
</pre>