Purchase requisition events

[Rob Lake]

Felix,
 
If you're on release 4.6A or higher you can use transaction SWB_COND =
(under
Business Workflow - Development - Definition tools - Events - Event
linkages) to define additional start conditions for the event linkage.
 
For example, you could have an event for each line item but only =
trigger a
workflow for the first item by entering its number as a start =
condition.
 
This should save you having to make changes to objects or programming =
your
own events (as long as you have release 4.6)
 
Rob Lake
Procurement and Supply Process Development, Nestl=E9 UK Ltd
Tel: +44 (0)1904 604961, e-mail: Robert.Lake at uk.nestle.com
 
-----Original Message-----
From: Patrik vanOdijk [mailto:patrik.van.odijk at gbg.frontec.se]
Sent: 09 May 2000 09:49
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Purchase requisition events
 
 
Hi Felix,
 
It's not easy to solve this. What we did was to create a new method for
bseg_mmiv that triggered only one event for all events triggered. We =
then
had a
single step task with this method that was triggered from all blocking
reasons.
The method cancelled out all events and triggered only one (for line =
item
001).
You then also need to create a new event for bseg_mmiv that the new =
method
can
trigger. The problem with this solution is how to cancel out the =
correct
events
and only get one event., but it is possible.
 
It's a bit "dirty" solution but it works.
 
Good luck,     Patrik van Odijk
 
 
 
 
 
"Hassine, Felix" <Hassine.Felix at PMINTL.CH> on 2000-05-08 17:32:53
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Patrik van Odijk/GBG/FRONTEC)
 
Subject:  Purchase requisition events
 
 
 
 
Hi all,
 
        We need to create 1 workflow instance when a purchase =
requisition is
created with the blocking flag on. Only 1 should be started, but the =
system
generates as many events as line items in the workflow. As a result, my
workflow may start several times, which is not the desired effect.
 
I have tested the "overall" release button in the customizing (Purchase =
Req
release Strategy), but then no event al all is then generated.
I have also attempted to create a "change" doc for change document =
class
"BANF" , but it works only for CHANGED status, not for CREATE.
 
Has anybody experienced the same problem ?
 
Thanks for any clue.
 
Felix Hassine