Deleting work item

Tue Sep 9 05:36:01 EDT 2008

Hi,

Thanks lot for All your information! 

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.

If possible could please send me step by step process for this activity.

Regards
Muralitharan C
Tata Consultancy Services
Mailto: muralitharan.c at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Outsourcing
____________________________________________

"Florin Wach" <florin.wach at gmx.net> 
Sent by: sap-wug-bounces at mit.edu
09/09/2008 02:26 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To
"SAP Workflow Users\' Group" <sap-wug at mit.edu>
cc

Subject
Re: Re: Deleting work item

addendum:

plus, you can use under  Basic-Data-->Workflow dependent settings-->Events 
the
BUS2105 / AllReleaseReset / 1 Cancel Workflow   entry  (as stated by 
Aghrip in the SDN Forum Thread)

-------- Original-Nachricht --------
Datum: Tue, 09 Sep 2008 10:21:18 +0200
Von: "Florin Wach" <florin.wach at gmx.net>
An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
Betreff: Re: Deleting work item

Hello,

please check WS20000077 Node #4 "Overall release of requisition", 
referring to TS20000159 BUS2105.SingleRelease and terminating events:
REJECTED
RELEASED
RESET
SIGNIFICANTLYCHANGED

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.

Your event .Changed is probably triggered to often, so I'd recommend to 
use the .ReleaseStepCreated event only to start the workflow (again).

With your workflow pattern:
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.

So long & take care,
   Florin

-------- Original-Nachricht --------
> Datum: Tue, 9 Sep 2008 13:18:48 +0530
> Von: muralitharan.c at tcs.com
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> CC: "SAP Workflow Users\' Group" <sap-wug at mit.edu>, 
sap-wug-bounces at mit.edu
> Betreff: Re: Deleting work item

> Hi,
> 
> I have modified PR Me52n and checked through swels and swel shows 
> "Significant change" event is not triggered as shown.
> 
> 
> But through parallel step where do we implement this parallel process in 

> my workflow,as given below
> 
> please suggest me and give me details if possible.
> 
> If you have other difficulties here, because you're using your own 
custom 
> workflow pattern, I'd advice to create a new event 
BUS2105.AllReleaseReset
> and create this through the change documents BANF, restriction field: 
> EBAN-FRGZU_OLD <> ' '  and EBAN_FRGZU_NEW = ' '  and use this event to 
> terminate the complete existing workflow by a parallel step with an 
> event-item listening to this particular event.
> 
> This is my workflow steps,
> 
> 
> Muralitharan C
> Tata Consultancy Services
> Mailto: muralitharan.c at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty.   IT Services
>                         Business Solutions
>                         Outsourcing
> ____________________________________________
> 
> 
> 
> "Florin Wach" <florin.wach at gmx.net> 
> Sent by: sap-wug-bounces at mit.edu
> 09/09/2008 12:38 PM
> Please respond to
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
> 
> 
> To
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
> cc
> 
> Subject
> Re: Deleting work item
> 
> 
> 
> 
> 
> 
> Hi,
> 
> The SAP Standard will raise the event .SignificantlyChanged for obsolete 

> work items. You'll need to correct and check your terminating events.
> There can also be release dependent difference (especially on systems 
> before 4.70), so please check also your event log (activated for 
BUS2105).
> 
> If you have other difficulties here, because you're using your own 
custom 
> workflow pattern, I'd advice to create a new event 
BUS2105.AllReleaseReset
> and create this through the change documents BANF, restriction field: 
> EBAN-FRGZU_OLD <> ' '  and EBAN_FRGZU_NEW = ' '  and use this event to 
> terminate the complete existing workflow by a parallel step with an 
> event-item listening to this particular event.
> 
> The new workflow instance will be started by the 
> BUS2105.ReleaseStepCreated as usual.
> 
> Best wishes,
>    Florin
> 
> -------- Original-Nachricht --------
> > Datum: Tue, 9 Sep 2008 12:14:07 +0530
> > Von: muralitharan.c at tcs.com
> > An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> > Betreff: Deleting work item
> 
> > Hi Friends,
> > 
> > I'm having a issue in purchase requisition(PR) workflow, actually when 

> PR 
> > is created then work item is generated in SAP inbox to  approver(A) 
and 
> > approved  then work item will be send to second level approver (B) 
then 
> > work item lies in second approver(B) level in between this time PR 
> > creator(Intial Stage) modify the PR with the value then new release 
> > strategy will be generated and Once again from first level the process 

> > will be taken place then work item go to  first approver A and 
approved 
> > then go to second level B here already existing work item for this PR 
> will
> > be there as well generated one so dual work item is lying.
> > 
> > Now I need to delete this work item from sap in-box in second level B 
> > approver whether it's possible or not How come handle this situation?
> > 
> > Please provide me solution for this scenario.
> > 
> > Regards,
> > 
> > Muralitharan C
> > Tata Consultancy Services
> > Mailto: muralitharan.c at tcs.com
> > Website: http://www.tcs.com
> > ____________________________________________
> > Experience certainty.   IT Services
> >                         Business Solutions
> >                         Outsourcing
> > ____________________________________________
> > =====-----=====-----=====
> > 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
> > 
> > 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> ForwardSourceID:NT00007FCE 
> =====-----=====-----=====
> 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
> 
> 
_______________________________________________
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

ForwardSourceID:NT00007FE6 
=====-----=====-----=====
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080909/c6b05d53/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 20825 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20080909/c6b05d53/attachment.gif