Triggering event with conditions?

[Mr Ravi Shankar]

Hi Kevin,
  There might be little catch in this approach if you
are using a check function module for the parked
document scenarion in pre - 46C systems ( I don't
check it in 46C system ). In the check FM/ Receiver Fm
- you can't write code to check for the some data
which will not be written to the database until little
later. You can check OSS on this.
 
One way to get around this is using the user-exit
available.
 
Let me know if you need any more info.
 
Ravi
 
 
--- "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:
> Hi Kevin,
> Just to add my two cents worth...
>
> My current view is that:
> If you are in 4.6 and have access to start
> conditions (transaction SWB_COND
> in
> an R/3 system, SWB_PROCUREMENT in EBP systems)
> and you can figure out which workflow to start with
> a logical expression,
> e.g. Parked_document.doc_type = 'XX',
> then use start conditions, because:
>
> 1. It's configuration - you don't need to write any
> code.  Activating the
> event
> linkage via the start condition automatically adds
> the matching standard
> check
> function module to your event linkage (very nice).
>
> 2. It's easy for users/super users/other workflowers
> to see and understand
> what you have done.
>
> 3. It's easy to change later on if your business
> rules change.
>
> 4. You can be as complex as you like with your
> logical expression as the
> start condition editor handles parentheses, logical
> and/or/not, etc. - so
> you have
> quite a bit of flexibility as well.
>
> If you are pre-4.6 or deciding which workflow to run
> is not as simple as a
> logical
> expression, you can use either check function
> modules or receiver type
> function modules
> - either will do.  However, if you want to be sure
> that you start at least
> one
> of the workflows every time, then the receiver type
> function module would
> make more sense.
> If you don't care, then it doesn't matter but their
> might be less coding
> involved in
> writing a receiver type function module.  On the
> other hand people are
> usually more
> used to writing check function modules so you might
> find it easier to do
> that.
>
> Above all, DON'T create a super workflow that just
> evaluates a condition,
> and then
> starts the appropriate sub-workflow.  It's bad for
> performance due to all
> those extra
> and unnecessary super workflow instances.
>
> Hope that helps.
> Regards,
>         Jocelyn Dart
> Consultant (BBP, Ecommerce, Internet Transaction
> Server, Workflow)
> SAP Australia
> Email jocelyn.dart at sap.com
> <mailto:jocelyn.dart at sap.com>
> Tel: +61 412 390 267
> Fax: +61 2 9935 4880
>
>
>
> -----Original Message-----
>> From: Kevin Yu [mailto:kevin.yu at its.monash.edu.au]
> Sent: Friday, 22 June 2001 3:50 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Triggering event with conditions?
>
>
> I do not know if this is possible or not.  That's
> the reason I send this
> message to see if anyone can tell me!
>
> Here is the scenario, for example, I have three
> workflows all triggered
> by Parked document created.  The three workflows all
> have different
> tasks to perform based on document types.
>
> Is it possible to put a condition against the
> triggering event such that
> for certain document types only the corresponding
> workflow will be
> triggered. Or, I have to build all these three
> workflows as
> sub-workflows and called by a workflow which
> triggered by parked
> document created.
>
> Regards,
 
 
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/