BUS2012 and event RELEASED and RELEASESTEPCREATED

[Kjetil Kilhavn]

Are you sure the problem is with the workflow and not with the event creation? Turn on the event log (I recommend you set a filter on object type) to determine if the problem is missing events or non-starting workflows. Since the simulation is OK it appears the problem is missing events.
 
If the event is not created, could there be something wrong in the release strategy? We don't use release strategies, so I can't help you there.
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS
 


________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of koenraad.janssens at arcelor.com
Sent: 13. oktober 2005 14:53
To: sap-wug at mit.edu
Subject: Re: BUS2012 and event RELEASED and RELEASESTEPCREATED



Did you check the event queue? (sweqadm) 
And transactional rfc (sm58)? 

Met vriendelijke groeten,
Salutations,
Best regards,
Mit freundlichen Grüssen,
Atentos saludos, 



	ineke.hopman at nl.ibm.com 
Sent by: sap-wug-bounces at mit.edu 

13/10/2005 14:30 
Please respond to sap-wug 


        
        To:        sap-wug at mit.edu 
        cc:         
        Subject:        BUS2012 and event RELEASED and RELEASESTEPCREATED




Hello, 

We have a purchase order release flow that starts on event releasestepcreated and stops with event released. 
Every thing worked fine, untill today. 

The event is not triggered any more if a PO gets in a releasestep or the PO is released....?! 
We checked swe2 and swe3, the linkage is active. 
Simulate the event with trx swue, works fine. 
There are no errors in swu2 or relevant dumps found in st22. 
It looks like we miss something basics, can any one tell if there is another transaction in the system were the event is activated? 

Thanks for helping! 

Kind regards, 
Ineke Hopman


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051013/3bd0a18e/attachment.htm