Purchase requisition events

[Stephan Becker]

completing my earlier posting, the below works but could mean a significant
performance overhead for your system, depending on the number of po's and
line items within them. since every event will first start a workflow and
thus create multiple transactional rfc's, you could be looking at hundreds
of workflows started within a very short time-frame (all but one would be
cancelled shortly afterwards), which could mean general performance
impairment.
the solution with the check function module circumvents that as the check
function module runs in the context of the caller (the application), not the
recipient (the workflow). The workflow only gets started when the check
function module raises no exception.
stephan becker
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Patrik vanOdijk
Sent: 09 May 2000 10: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