Picking up the changes outside the current workflow's key fields data

[Ricky Lee]

Hi Ulrich,
 
Thanks for the reply
My Questions is:
When I put the Wait for Event task in my workflow, it seems that it only =
listens to the object (with that object's key field) and it does not =
pick up other changes (like the changes made by other applicant, or =
vacancy deleted {no more vacancy existed all related workflow should all =
be terminated})
 
I meant I can deal with that by the coding but I would think thats =
messy. Soo just want to find out whether there is a more  configuration =
way doing it. Besides, I think SAP should think of that already. I guess =
I might be the only person in the world doesn't know this yet ...
 
Ricky Lee         =20
SAP Developer, Product Development=20
Proteus Solutions=20
Direct: +61 2 8273 8190=20
Email:  ricky.lee at proteussolutions.com.au=20
http://www.proteussolutions.com.au=20
 
This message transmitted on 100% recycled electeons
 
IMPORTANT NOTICE=20
-------------------------------=20
This electronic mail message is intended only for the named =
recipient(s). If you have received this message in error, you are =
prohibited from reading, copying, distributing or using the information. =
Please contact the sender immediately via return e-mail and destroy the =
original message.
 
The contents of this message should not be relied upon by any person =
without subsequent written confirmation. The Firm accepts no liability =
for actions taken as a result of this message prior to receiving such =
written confirmation.=20
 
 
 
-----Original Message-----
From: Ulrich Mende [mailto:wug at mende-edv-beratung.de]
Sent: Thursday, 28 March 2002 6:08 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Picking up the changes outside the current workflow's key
fields data
 
 
Hi Rick -
yes, in SAP it is a standard scenario, that a workflow must react on
changes that are made from outside.
First you have to ensure that your application A will generate the
event(s) you can wait for in the workflow. Set your event trace to ON
and check weather events are created or not.
Then you have to insert a fork 1(2) (2 parallel branches, 1 of which
must be completed before the workflow continues)  in your workflow. In
the first branch sits transaction B, in the second branch insert the
wait step. This step needs an object instance. Take the same instance,
that will be used by transaction B in branch 1. You can set it up via F4
from the workflow container. Set up the event you are waiting for
(CHANGED, COMLPETED...). Set the count of events to wait for to 1.
 
Best regards Uli
 
 
 
Ricky Lee <ricky.lee at proteussolutions.com.au> schrieb am 28.03.2002,
01:29:09:
> Hi Everyone,
>
> Just wondering is it possible to set up a Wait for Event that will =
pick up the changes made outside the current workflow's key fields? E.g. =
In my Recruitment Workflow, Applicant A and B both apply for same =
vacancy. I need to terminate the Applicant B workflow when Applicant A =
receives the contract offer and fill the vacancy position. soo I want to =
find out whether it is possible to set up a Wait for Event that will =
pick up the changes (when Vacancy is filled).
>
> I am on 46C.
>
> Any help is appreciated
>
> Ricky Lee