Help on terminating events

[Dart, Jocelyn]

Hi Irene,
Try looking at the standard workflow WS00000038 for an example on how they use the significantlychanged event.
Alternatively you can either:
* use a fork at the start of your workflow to on one side run your process and on the other wait for terminating events
- i.e. if you want to close the current workflow if that event occurs
* add the event as a terminating event of the affected task - i.e. if you just want to close the current work item if that event occurs
 
For WAS systems such as R/3 4.7 you can also define terminating events in the Basic Data section of the workflow.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: Paulino, Irene [mailto:Irene.Paulino at kcc.com]
Sent: Wednesday,8 October 2003 11:12 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Help on terminating events
Importance: High
 
 
"Query :"
 
It has been a long time since I did workflow development.  I need help with
terminating events.
 
A req approval workflow is triggered when we create a requisition using
business object BUS2009. Now when changes happen to the requisition,
business object BUS2105 event SIGNIFICANTLYCHANGED is triggered.
 
Objective is to kill/terminate the work item generated upon creation of
requisition and then generate a new one with business object BUS2105. From
what I can remember, we can do terminate work items via terminating events.
 
Can anybody pls confirm or guide me as to how I should do this.
 
Assistance much appreciated.
 
Cheers,
Irene Paulino
Senior Analyst/Workflow admin
Kimberly-Clark Asia Pacific
 
-----Original Message-----
From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
Sent: Wednesday, 8 October 2003 10:42 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: LIV - Method to release invoice in background
 
 
G'day all,
 
we are in 4.6c
 
I am building a workflow to handle MM invoices blocked for quantity
reasons.
 
The workflow will send a work item to someone and after this someone
executes one of the options the next step is to run report RM08RELEASE
(Release Blocked Invoices - transaction code MRBR) in the background for
the relevant invoice number and setting radio button 'Release
automatically'.
 
Not being very successful!
 
I am still figuring out what method BUS2081.ReleaseSingle does? Maybe it
does what I am trying to do?
 
I wrote a little method that looks like this:
 
SUBMIT RM08RELEASE
    WITH SO_BUKRS-LOW = '1000'
    WITH SO_BELNR-LOW = object-key-invoicedocnumber
    WITH  SO_GJAHR-LOW = object-key-fiscalyear
   WITH PA_XMANU = ''
   WITH PA_XAUTO = 'X'
    EXPORTING LIST TO MEMORY
   AND RETURN.
 
The report runs okay but it does show me the output screen (e.g 'Blocking
reasons deleted in 0 lines' message is displayed in the bottom of the
screen), and I would like to avoid that (that's why I used EXPORTING LIST
TO MEMORY). I just want to run the report for that invoice and later in my
workflow I will check if the block was removed or not.
 
Any other ideas?
 
Thanks and regards
 
Cristiana
 
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error, please
inform us promptly by reply e-mail, then delete the e-mail and destroy any
printed copy.   Thank you.
 =============================================================================