BAPI_REQUISITION_DELETE

Thu May 23 14:04:28 EDT 2013

Hi Carolyn,

Yes, because release strategy would change.
Your release strategy is certainly based on value so to avoid it you should make some starting condition and may be in the release classification.

I hope that helps

Cheers
Stéphane

sap-wug-request at mit.edu a écrit :

>Send SAP-WUG mailing list submissions to
>	sap-wug at mit.edu
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://mailman.mit.edu/mailman/listinfo/sap-wug
>or, via email, send a message with subject or body 'help' to
>	sap-wug-request at mit.edu
>
>You can reach the person managing the list at
>	sap-wug-owner at mit.edu
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of SAP-WUG digest..."
>
>
>Today's Topics:
>
>   1. BAPI_REQUISITION_DELETE (Carolyn A Fuller)
>   2. Re: BAPI_REQUISITION_DELETE (Carolyn A Fuller)
>   3. Comments Box on the UWL (Colm.Gavin at kerry.ie)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 23 May 2013 13:50:31 +0000
>From: Carolyn A Fuller <fuller at MIT.EDU>
>Subject: BAPI_REQUISITION_DELETE
>To: "SAP Workflow Users' Group" <sap-wug at MIT.EDU>
>Cc: Kristen Hann <khann at mit.edu>
>Message-ID:
>	<ACD2E18075558E40920596957B5F324710CE2843 at OC11expo28.exchange.mit.edu>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi all,
>
>I am about to go into a meeting to discuss the root cause of what happened last night when thousands of workflows were kicked off for very old requisitions. The program that seems to have caused this problem calls the BAPI_REQUISITION_DELETE and marks each line item for a requisition as closed.
>
>Is there any way this could trigger the event RELEASESTEPCREATED? 
>
>---------------------
>Carolyn Fuller
>fuller at mit.edu
>
>
>
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130523/ebdc6636/attachment-0001.htm
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: smime.p7s
>Type: application/pkcs7-signature
>Size: 1582 bytes
>Desc: not available
>Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20130523/ebdc6636/attachment-0001.bin
>
>------------------------------
>
>Message: 2
>Date: Thu, 23 May 2013 15:09:55 +0000
>From: Carolyn A Fuller <fuller at MIT.EDU>
>Subject: Re: BAPI_REQUISITION_DELETE
>To: "SAP Workflow Users' Group" <sap-wug at MIT.EDU>
>Message-ID: <E812F5F8-D63D-4AC2-92A0-093040C2598C at mit.edu>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi again,
>
>We discovered the problem. The requisition line items were associated with cost objects whose funds center had changed since the req was created. The BAPI, in closing the requisition, registered the change to funds center which in turn triggered the event. When manually closing a req associated with such a cost object, the change to funds center is not registered so the event is not triggered.
>
>I am hoping that SAP will change the BAPI so that it behaves the way the manual process behaves.
>
>Carolyn Fuller
>Sent from my iPad
>
>On May 23, 2013, at 9:50 AM, "Carolyn A Fuller" <fuller at mit.edu<mailto:fuller at mit.edu>> wrote:
>
>Hi all,
>
>I am about to go into a meeting to discuss the root cause of what happened last night when thousands of workflows were kicked off for very old requisitions. The program that seems to have caused this problem calls the BAPI_REQUISITION_DELETE and marks each line item for a requisition as closed.
>
>Is there any way this could trigger the event RELEASESTEPCREATED?
>
>---------------------
>Carolyn Fuller
>fuller at mit.edu<mailto:fuller at mit.edu>
>
>
>
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130523/d2ffa265/attachment-0001.htm
>
>------------------------------
>
>Message: 3
>Date: Thu, 23 May 2013 16:14:14 +0100
>From: Colm.Gavin at kerry.ie
>Subject: Comments Box on the UWL
>To: sap-wug at MIT.EDU
>Message-ID:
>	<OF1CF3E6FB.458C0CD7-ON80257B74.005371F7-80257B74.0053B388 at kerry.ie>
>Content-Type: text/plain; charset="us-ascii"
>
>Jocelyn,
>
>Thanks so much for your speedy response, we have done all the steps you 
>mentioned, along with writing the WebDynpro (which I've tested in SE80 and 
>it works), but when I click on the button to trigger the dynpro, I get an 
>error called "Internet Explorer cannot display the webpage", is there 
>anything obvious that I may be missing on this?
>
>Thanks again,
>Colm
>***************************************************************************************
>The information transmitted is intended only for the person or entity to which it is 
>addressed and may contain confidential and/or privileged material. Any review, 
>retransmission, dissemination or other use of, or taking of any action in reliance 
>upon, this information by persons or entities other than the intended recipient is 
>prohibited and may be unlawful. Kerry Group accepts no liability for actions or effects 
>based on the prohibited usage of this information. Kerry Group is not liable for the 
>proper and complete transmission of the information contained in this communication or 
>for any delay in its receipt. If you received this in error, please contact the sender 
>and delete the material from any computer. 
>
>Thank you for your attention.
>***************************************************************************************
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130523/ee773a9b/attachment-0001.htm
>
>------------------------------
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>End of SAP-WUG Digest, Vol 102, Issue 21
>****************************************