Performance example

[Dart, Jocelyn]

Hi Folks, 
Let's be clear here:
 
Event plus START CONDITION - i.e. transaction SWB_COND - A start
condition is part of the event linkage, evaluated before workflow,
configuration only, uses and automatically defaults in a STANDARD event
check function module - all good.
 
Own check function module - may or may not be better for performance but
certainly worse for TCO, clarity, future changes, etc. - only use if you
really have to and you shouldn't have to - lukewarm. 
 
Event plus CONDITION as a step at the beginning of your workflow -
condition happens after workflow starts - i.e. unnecessary workflows
started - bad. 
 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Breslavets Sergey
Sent: Thursday, 06 April 2006 3:23 AM
To: SAP Workflow Users' Group
Subject: RE: Performance example


Hi Richard,
 
use the standard events and event check function module instead of the
starting conditions (it's executed even before the event is started).
It's more efficient then conditions, and easier to maintain then user
exit.
 
Serge
 
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Smart, Richard
Sent: Wednesday, April 05, 2006 10:52 AM
To: sap-wug at mit.edu
Subject: Performance example



Just looking for some guidance here on the following example:

If a workflow is to be triggered for a certain sales organization when a
sales order undergoes a credit block, which of these 2 routes is the
best to take?

 

1)       Use the events BUS2032.CREATED or BUS2032.CHANGED and put a
start condition in the workflow.

2)       Trigger a new event from a user exit within the sales order. 

 

Which of these approaches is best?

 

Thanks

Richard

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