AW: Event for Purchase Requisition create

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi Kevin,
 
note that it will be necessary to run a release of Purch.Reqs if you
activate mentioned release strategies!
This may have impact to your bussiness processes.
 
Regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
Sue Keohan
Gesendet am: Freitag, 5. November 2004 01:10
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Event for Purchase Requisition create
 
Hi Kevin,
 
As I recall, the event ReleaseStepCreated is raised when a purchase
requisition meets the criteria you have  defined in your release
strategies.  That configuration is done through transaction OMGQ (or at
least it used to be).
 
Regards,
Sue
 
 
Kevin Wilson wrote:
 
>When we use ME51N to create the Purch Req this event is not kicked
>off.... Does it need to be enabled in config?
>
>-----Original Message-----
>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
>Farnes, Randee
>Sent: Thursday, November 04, 2004 3:57 PM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Event for Purchase Requisition create
>
>Use the event 'ReleaseStepCreated'.
>
>-----Original Message-----
>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
>Kevin Wilson
>Sent: Thursday, November 04, 2004 2:50 PM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Event for Purchase Requisition create
>
>I am trying to start a workflow whenever a purchase requisition is
>created (ME51N). No change documents are generated when it's created =
and
>there is no user exit called that has the Purch Req number in it in
>order to explicitly raise an event. Any ideas on other methods to =
start
>a workflow for the objectBUS2105 (Purchase Requisition)?
>
>Thanks
>Kevin
>
>
>-----------------------------------------------------------------------=
-
>------
>
>This email is confidential and may be legally privileged.
>
>It is intended solely for the addressee. Access to this email by =
anyone
>else, unless expressly approved by the sender or an authorized
>addressee, is unauthorized.
>
>If you are not the intended recipient, any disclosure, copying,
>distribution or any action omitted or taken in reliance on it, is
>prohibited and may be unlawful. If you believe that you have received
>this email in error, please contact the sender, delete this e-mail and
>destroy all copies.
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 
>=3D=3D=3D=3D=3D=3D
>
>
>