Event Queue constraints

[Dart, Jocelyn]

Hi Ed,
As the event queue is there to help with high volume situations, suggest you use the event queue for your scenario 1.

For scenario 2 you might be better off putting a condition on your first workflow step (no not a start condition on the workflow - use the condition options on the workflow step itself) so that it waits if there are any other personnel change events being processed at the same time,  then schedule the condition job that reassesses the conditions at your 15-20 minute interval.

I'm sure there are other options that others have tried for scenario 2 also...
Regards,
Jocelyn

From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf Of Edward Diehl
Sent: Tuesday, 6 September 2011 11:37 PM
To: sap-wug at MIT.EDU
Subject: Event Queue constraints

Transaction SWEQADM

It appears that the background event delivery schedule is generic; that is, I can't set a different number-of-events/time schedule for individual event linkages.

Am I overlooking something?

Has anyone out there dealt with this?

The problem is I have two totally different classes of workflows in terms of execution performance.
1 - Lots of events (thousands) coming in through an interface with changes to the material master, mostly for adjusting purchase reqs and purchase orders, and
2 - A smaller number of personnel change events that trigger VERY complex workflow(s) with lots of database updates.

1 - needs to process 50 - 100 events at a time with a 5 min queue read interval.
2 - needs to process 1 event at a time with a 15-20 min interval.

I would appreciate any thoughts on this.

Thanks,
Ed Diehl


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110907/3d6092d0/attachment.htm