Purchase requisition events Hi Felix, The only thing I can think of is if you are using the value of the requisition in your realease strategy. I would change the classification entry from CEBAN-GSWRT (item value) to CEBAN-GFWRT (total value). Phil ______________ Reply Separator _ Subject: RE: Purchase requisition events Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US Date: 09/05/00 08:00 Philip, I have tried this , but it completely cancels the release strategy (i.e." the PR is not blocked any longer). Is there an additional trick ? Felix > -----Original Message----- > From: Kisloff, Philip (BE) [SMTP:pkisloff@dc.com] > Sent: Tuesday, May 09, 2000 2:39 AM > To: "Hassine; Felix" > Subject: RE: Purchase requisition events > > Felix, > > Not only do you have to check the flag in transaction OMGS, but > also the "OverReqRel" for document type in transaction OMEB. The > event created now belongs to business object BUS2105 (change from > BUS2009 for item level). > > Hope this helps > > Philip Kisloff > Deloitte Consulting > Oberwil-CH. > > > Reply Separator > ___________________ > Subject: Purchase requisition events > Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US > Date: 08/05/00 11:32 > > > 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 >

Philip Kisloff pkisloff at dc.com
Tue May 9 11:45:26 EDT 2000