BAPI_REQUISITION_DELETE

[Carolyn A Fuller]

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.htm