Standard SAP events have 'stopped'

[Stephan Becker]

I have sometimes had a buggered generation of a business object cause such
behaviour. This buggering-up (technical term <g>) can be caused among other
things by a change to the system (e.g. a kernel change) that would normally
result in a re-generation of the business objects, and for some weird reason
that didn't work for the object at hand (a foreign lock may be a cause for
that).
 
Try re-generating the object and let us know whether it did the trick; this
is one of the interesting "strange" workflow errors that can easily throw
you back a week if it occurs in a project..
 
Thanks,
Stephan Becker
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Markus Brahm
Sent: 24 March 2000 11:34
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Standard SAP events have 'stopped'
 
 
Hi Rob,
 
have you checked the transactional RFC monitoring (SM58) for any error
messages
that might help you? Have you specified a special destination for your event
creation in SWE2 and is the gateway to this destination overloaded?
 
Best regards,
 
Markus
 
 
 
 
 
 
 
Rob Lake <Robert.Lake at nestlegb.nestle.com> on 24.03.2000 10:44:31
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Markus Brahm/PLZ/CSC)
 
Subject:  Standard SAP events have 'stopped'