Event queue - not a problem, just well... strangeness

[michael.mcley@daimler.com]

Sue,

Thanks for your answer, it got me looking into the actual method call of 
the first task in the workflow - that's were the problem is.  I guess 
instead of looking into a 100% custom BO method written by one of our 
biggest hack developers, I assumed that I had uncovered a bug in SAP 
standard that no one else had reported in what, 10 years?  Stoo-pid. Sorry 
for wasting your time but thanks again ;-)
 
Michael McLey 
MBUSI - IT Parts & Administration 
Mercedes-Benz US International, Inc. 
1 Mercedes Drive 
Vance, AL 35490 
PHONE:  (205) 462 - 5239 
EMAIL:   michael.mcley at daimler.com   



Sue.Doughty at odfl.com 
Sent by: sap-wug-bounces at mit.edu
05/05/2010 03:26 PM
Please respond to
sap-wug at mit.edu


To
sap-wug at mit.edu
cc

Subject
RE: Event queue - not a problem, just well... strangeness






Hi Michael,
 
I just tried the same event with the invalid key and the event delivered 
properly.  When the workflow that was triggered started, it went into 
error status because the trip did not exist.
 
Do you have the Event trace turned on?  If not, turn it on (SWELS for that 
specific event) long enough for your event to be triggered again.  When 
you look in the Event trace in SWEQADM, you can double click the event 
that you had the issue with and in the Receiver Data section you will see 
if there were any error messages.
 
There could be an issue in the Workflow’s Header section under Start 
Events that is not allowing the workflow to start.
 
Regards,
Sue
 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of michael.mcley at daimler.com
Sent: Wednesday, May 05, 2010 3:54 PM
To: sap-wug at mit.edu
Subject: Event queue - not a problem, just well... strangeness
 

Wuggers,

Here is an issue which has probably been discussed before, but I cannot 
seem to find an answer for it.

With a few of our workflows, we use the event queue.  And of course the 
background job (SWEQSRV - running program RSWEQSRV) dequeues the events 
and triggers the workflows.  I think most people here are familiar with 
this process.

The wierd thing is, if I have an event in the queue (which I think is 
actually table SWEQUEUE) with an invalid key (in my case BUS2089-CREATED 
with key whatever - 999999999999999999, when the job runs, it will create 
a new event with key 000000000000000000 of the same object and event. This 
new event also has an invalid key, and so will keep generating a new event 
with each run of the batch job (the events do not stack up, it just 
removes the old one and replaces it with a new event).

Is this normal behavior for this program?  Can this behavior be changed 
(maybe to not generate a new event)?  Any similar experiences?
Michael McLey
MBUSI - IT Parts & Administration 
Mercedes-Benz US International, Inc.
1 Mercedes Drive 
Vance, AL 35490 
PHONE:  (205) 462 - 5239 
EMAIL:   michael.mcley at daimler.com   
If you are not the intended addressee, please inform us immediately that 
you have received this e-mail in error, and delete it. We thank you for 
your cooperation. 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100506/02a37b5d/attachment.htm