Event trigger for MRP related purchase requisitions

[Enrique Arreguin Ramirez]

Hi Matt:
 
This is a "MRP performance" related issue. We are in 4.0B versi=F3n and =
we had
to go through the path "reservation then planned order then purchase
requisition" so the event would raise. Search in OSS with MRP and
performance.
 
Saludos.
Enrique Arregu=EDn Ram=EDrez
     Inform=E1tica AHMSA
Monclova, Coahuila. M=E9xico
 J      (866) 649-3330  Ext. 3752, 3707
 e-mail : earreguinramirez at gan.com.mx=09
 
 
 
 
-----Original Message-----
From: Corrin, Mat [mailto:Mat.Corrin at atosorigin.com]
Sent: Thursday, October 10, 2002 5:06 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event trigger for MRP related purchase requisitions
 
 
Hi all,
 
I have a workflow that is triggered by the event
PurchaseRequisition.releaseStepCreated. This works fine for those =
purchase
requisitions that are generated via a sales order. However, when a
requisition is generated via MRP, the event trace shows that this event =
is
not raised. Both types of requisition are subject to the same release
strategy.
 
Any ideas why the event is not raised for MRP related PR's ?
 
Thanks,
 
Mat.
 
Mat Corrin
Development Consultant
Atos Origin UK
 
 
************************************************************************=
****
******************************************************
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.  The views =
expressed
in this electronic transmission do not necessarily reflect those of =
Atos
Origin or any of its subsidiary companies. Although the sender =
endeavours to
maintain a computer virus free network, the sender does not warrant =
that
this transmission is virus-free and will not be liable for any damages
resulting from any virus transmitted.  Thank You.
************************************************************************=
****
******************************************************