Purchase requisition events

Hassine, Felix Hassine.Felix at PMINTL.CH
Mon May 8 16:25:25 EDT 2000


Everaldo,
 
Thanks for your response. It helps in that it confirms me that this is not
an easy task.
SAP has designed the whole thing to treat PR items, I have realized this
too. But
I thought it could be bypassed, since this is what our business users need.
A PR can contain
several items , and there is no desire to have them agreeing and commenting
5 or 10 times the
same request for compound orders.
 
I will  try to find my own logic to do this. But encapsulating ME51 is not
in the scope, because it
means creating some change in the standard, which is not in my plans.
 
Thanks again for your response.
 
Best regards,
 
        Felix
> -----Original Message-----
>> From: Everaldo Biselli [SMTP:ecandolo at br.ibm.com]
> Sent: Monday, May 08, 2000 8:39 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Purchase requisition events
>
> Hi Felix,
>
> The SAP R/3 works with the purchase requisition item and not with the
> purchase requisition. As far as I know, until release 40B, there was no
> change document that was sensitive for purchase requisition events, it
> just
> works for purchase requisition items. There was no user exits in the
> transaction that create purchase requisitions (ME51) that can be used too.
> In  my opinion, you should create a new Business Object that has  in the
> key only the purchase requisition number, create a new event in this
> object, and activate this event using the ABAP function module
> SWE_EVENT_CREATE. But you should create too a new transaction that
> encapsulates the standard transaction (ME51) and after calling this
> transaction you will include the CODE for calling this event. That's in
> the
> only solution that I can find.
> As you can see this is a complex solution that includes ABAP development
> and some experience constructing workflows. Maybe should be better review
> the process and check if it's possible to change something to help you
> with
> this problem.
>
> Anyway, I hope that this information can help you.
>
> If you need any further information, just let me know.
>
> Everaldo.
>
> ________________________________
> Everaldo Luiz Candolo Biselli
>
> ecandolo at br.ibm.com
>
>
> "Hassine, Felix" <Hassine.Felix at PMINTL.CH> on 08/05/2000 14:32:53
>
> Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
>
> To:   SAP-WUG at MITVMA.MIT.EDU
> cc:    (bcc: Everaldo Luiz Candolo/Brazil/IBM)
> 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
 


More information about the SAP-WUG mailing list