Purchase Requisition release workflow (WS00000038)

[Flavio Oliveira]

I had this problem when I was working on 3.0F. The problem occurs only if,
after the requisition change, the release strategy remains the same. If the
release strategy changes, the event is being raised and WF works fine.
 
This is an SAP bug. I've contact SAP when I had the problem, they recognized
it but said that they could not solve it (until some release that I do not
remember).
 
To fix the problem I had to change the template to raise the event after the
requisition change. Resume: keep the release code in a container element
BEFORE the requisition change. AFTER the requisition change you compare the
new release code with the old one. If they are the same (SAP will not raise
the event), raise the event yourself. Otherwise, let SAP work as it should.
 
I hope this help... if you have any doubts, please let me know.
 
Flavio.
>From: "Bertrand, Scott" <scott.bertrand at sap.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Purchase Requisition release workflow (WS00000038)
>Date: Fri, 18 Oct 2002 16:59:52 +0200
>
>Hi Frank,
>
>Sounds like the MM release strategy is not configured correctly.  This is
>usually done by an MM person, as the classification and characteristic
>setup can be complex.
>
>Hope this helps,
>Scott
>
>Scott Bertrand
>Technical Consultant
>SAP America, Inc.
>
>3999 Westchester Pike
>Newtown Square, PA 19073
>T 610-661-1905
>F 610-661-1906
>E scott.bertrand at sap.com
>http://www.sap.com
>
>
>
>-----Original Message-----
>From: Frank Miller [mailto:Frank.Miller at capetown.gov.za]
>Sent: Friday, October 18, 2002 10:48 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Purchase Requisition release workflow (WS00000038)
>
>
>Hi,
>
>Yes, you are right in that there are no loops in this workflow, but
>what I mean is that the ME52N should also trigger the release workflow
>just as the ME51N does. This is my problem.
>
>Thanks.
>
>Frank Eriksen-Miller
>SAP Consultant
>Mobile: 072 472 6915
>Desk: (021) 400 - 4539
>
> >>> Stuart.Tainsh at atosorigin.com 10/18/02 03:10pm >>>
>Frank,
>This WF Template does not contain any loops, therefore the initial
>action on the Purchase Req. is only processed once.
>For notification to the Releaser that a change has been made, the Req.
>would need to be released again - thus retriggering the Event: BUS2009
>RELEASESTEPCREATED and starting the WF again.
>
>Regards,
>Stuart Tainsh
>
>
>Atos Origin - SAP Practice
>Senior Development Consultant
>* Office: +44 (0)1928 598862   Mobile: +44(0)7740 565602
>* Origin, P.O. Box 58, Daresbury Court,  Manor Park, Runcorn, Cheshire
>WA7 1FJ
>*    <mailto: Stuart.Tainsh at atosorigin.com>
>
>
>**********************************************************************************************************************************
>      This electronic transmission and any files attached to it are
>strictly confidential and intended solely for the
>      addressee.   If you are not the intended addressee, you must not
>disclose, copy or take any action in
>      reliance of this transmission.  If you have received this
>transmission in error, please notify us by return and
>      delete the same. Thank you.
>
>**********************************************************************************************************************************
>
>
>-----Original Message-----
>From: Frank Miller [mailto:Frank.Miller at capetown.gov.za]
>Sent: 18 October 2002 13:53
>Subject: Purchase Requisition release workflow (WS00000038)
>
>
>The following works:
>
>- On creation of an ME51N it sends a workitem to the Releasers
>mailbox.
>- The releaser then when executing the workitem now has the option of
>releasing or rejecting the message.
>- When he rejects the release request, it then creates an entry in the
>mailbox of the initiator.
>- the initiator when executing the workitem is now taken into an ME52N
>to make the required changes.
>
>Now, according to me, when the change has been made, it should create
>a
>workitem in the releaser's mailbox again to allow him to release or
>reject the Purch Req again, but this is not happening.
>
>Could someone please shed some light on why it does not work?
>
>Thanks.
>
>Frank Eriksen-Miller
>SAP Consultant
>Mobile: 072 472 6915
>Desk: (021) 400 - 4539
 
 
_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband.
http://resourcecenter.msn.com/access/plans/freeactivation.asp