Standard task TS 00007951 Purchase order change generates incorrectly a workflow item when an order/network is TECOed/Closed.

[Flavio Oliveira]

That is correct, but you know that this is not allways true... I've had come
cases (not only in WF) that SAP should work in one way, SAP people agreed
with me that SAP should work like that and, even so, they told me that they
will not fix the problem and I had to create some workaround...
 
So, if you cannot sove the problem via the "correct" way, try your own
way...
 
Flavio.
 
>From: "Kane, Rajiv" <Rajiv.Kane at conoco.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Standard task TS 00007951 Purchase order change generates
>         incorrectly a workflow item when an order/network is
>TECOed/Closed.
>Date: Tue, 21 May 2002 16:14:32 +0400
>
>Flavio,
>
>  HI!
>
>  Thanks for your help.
>
>  In this case I am using a standard task given by SAP. When using
>standard task ,I think, we should not be forced like this to code the
>receiver function module to prevent unnecessary work items. This work
>items/events should not be generated in the first place! This should be
>part of SAP standard.
>
>  Regards,
>
>  Rajiv Kane
>
>-----Original Message-----
>From: Flavio Oliveira [mailto:oliveiraflavio at hotmail.com]
>Sent: Tuesday, May 21, 2002 3:28 PM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Standard task TS 00007951 Purchase order change generates
>incorrectly a workflow item when an order/network is TECOed/Closed.
>
>
>Rajiv:
>
>I do not know the process itself, but if you cannot figure out why the
>event
>is being raised and the message is coming, you can use the receiver
>function
>module to verify if you need or not the message from this event and
>avoid it
>to go to the user.
>
>Flavio.
>
>
> >From: "Kane, Rajiv" <Rajiv.Kane at conoco.com>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Standard task TS 00007951 Purchase order change generates
> >     incorrectly a workflow item when an order/network is
> >TECOed/Closed.
> >Date: Tue, 21 May 2002 09:17:11 +0400
> >
> >hi!
> >
> >I am sending this message again as I did not receive any feedback for
>this.
> >Please intimate me if you have any leads on this one.
> >
> >  We are in 3.1H & will be upgrading to 4.6c shortly.
> >
> >  I have used the standard task 7951 for workflow Purchase Order change
>so
> >that the buyers will be notified if any change to quantities or dates
>of
> >non-stock components & external activities are carried out in a
>maintenance
> >order or network purchase requisition having a PO.
> >
> >  The moment workflow was activated for a order type/network type it
>was
> >noticed that at the time of Technically completing or Closing of
> >Maint.Order/Network system was initializing(making it Zero) the
>requirement
> >quantities of the non-stock components having a PO.A work item was
>going to
> >the buyers that the requirement quantity is changed from say"x" to
>"Zero".
> >After application of SAP Note 109654 the requirement quantity of a
> >non-stock item having a PO is not changed to initial value now at the
>time
> >of Technical completion/closing of Order/Network (it stays as it is-if
>it
> >was "x" before after TECO/CLSD also it is"x") but still the buyers are
> >receiving a work item telling them that the quantity is changed from
>"x" to
> >"zero"-why?How to overcome this ?According to me the buyer should not
> >receive any work item now.
> >
> >
> >Thanks in advance,
> >
> >Rajiv
>
>
>_________________________________________________________________
>Send and receive Hotmail on your mobile device: http://mobile.msn.com
 
 
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx