Triggering BUS2009 events (purchase requisitions)
Amit Levavi
amitlevavi at hotmail.com
Sat Mar 1 18:16:50 EST 2003
Hi Carolyn and Richard,
Sorry to interrupt your conversation, but I just thought it is important to
mention that the user exit you are talking about is (as Carolyn suspected)
only activated in the enjoy transactions. I would like to suggets an
alternative:
One can raise a workflow event based on Change documents (NOT status
management, which is not active for purchase requisitions!). Try using this
option for trapping a change in the cost center and raise an appropriate
event.
Good luck,
Amit
>From: Carolyn Fuller <fuller at MIT.EDU>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Triggering BUS2009 events (purchase requisitions)
>Date: Sat, 1 Mar 2003 11:11:36 -0500
>
>Richard,
>
>Thank you! This is perfect. It is exactly what we need to do.
>
>Carolyn
>
>At 9:01 AM -0600 3/1/03, Richard V Marut wrote:
>>Carolyn,
>>
>>What a coincidence, I did exactly the same thing. When the requisition
>>was created, it was triggered with 'releaseStepCreated'. Then if someone
>>changed the cost center, I triggered the 'significantlyChanged' event
>>and then the 'releaseStepCreated' and everything worked as expected. The
>>previous work item was removed from the user's inbox and the new
>>workflow routed to a different person.
>>
>>You should have no problem restarting the workflow from this use exit.
>>I've had this in place since October and we've been testing along and
>>have never seen any problems. We'll be going live with this one in
>>April.
>>
>>Richard...
>>
>>
>>-----Original Message-----
>>From: Carolyn Fuller [mailto:fuller at MIT.EDU]
>>Sent: Saturday, March 01, 2003 8:17 AM
>>To: Richard V Marut
>>Cc: Elda Prudden
>>Subject: RE: Triggering BUS2009 events (purchase requisitions)
>>
>>Richard,
>>
>>Thank you for the very rapid response!
>>
>>What we want to do is end one workflow with the
>>'significantlyChanged' and begin a new one with the
>>'releaseStepCreated' so that the req is removed from the old cost
>>collector's approver's in-box and is sent to the new cost collector's
>>approver's in-box.
>>
>>Were you just trying to end the workflow? Do you foresee any problems
>>with starting a new workflow from this user exit?
>>
>>Carolyn
>>
>>>Carolyn,
>>>
>>>Sorry it took so long to reply. I was at the airport in San Francisco
>>>and had to get on the plane.
>>>
>>>Yes, we are using the enjoy transactions ME51N and ME52N but you should
>>>be okay because this is the communication structure that's used
>>>throughout the entire purchase requisition process. I almost 100% sure
>>>you should have no problem with the older/other transaction.
>>>
>>>If the 'significantlyChanged' event gets raised and there hasn't been a
>>>previously 'releaseStepCreated' event, then it would just be ignored
>>>because a workflow would never have been started.
>>>
>>>This user exit took a little time to find but once I saw the fact that
>>>it involved the communication structure, I figured it was worth looking
>>>into. I don't think it shows up directly under the MM Purchase
>>>Requisition development class.
>>>
>>>Richard...
>>>
>>>
>>>-----Original Message-----
>>>From: Carolyn Fuller [mailto:fuller at MIT.EDU]
>>>Sent: Friday, February 28, 2003 3:28 PM
>>>To: rvmarut at EARTHLINK.NET
>>>Subject: Re: Triggering BUS2009 events (purchase requisitions)
>>>
>>>Richard,
>>>
>>>THANKS! I'm not an MM person and was told by my MM people that there
>>>wasn't a user exit available for this purpose! This is fantastic news.
>>>
>>>Opps! I just thought of something. Is this a user exit for the joy
>>>transaction? We are not using the joy transactions.
>> >
>> >Thanks,
>> >
>> >Carolyn
>> >P.S. If you triggered 'significantlyChanged' and didn't trigger
>> >'releaseStepCreated' did the workflow just end with no new workflow
>> >triggered?
>> >
>> >>Carolyn,
>>>>
>>>>In response to item #3, I previously needed to raise the
>>>>'significantlyChanged' event when the cost center changed. I did this
>>>by
>>>>using function module SWE_EVENT_CREATE within the communication
>>>>structure user exit. I believe it's EXIT_SAPLEBND_004, enhancement
>>>>M06B0005 but don't quote me because I'm not at the office at the
>>>moment.
>>>>
>>>>Richard...
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
>>>>Carolyn Fuller
>>>>Sent: Friday, February 28, 2003 1:56 PM
>>>>To: SAP-WUG at MITVMA.MIT.EDU
>>>>Subject: Triggering BUS2009 events (purchase requisitions)
>>>>
>>>>Hi all,
>>>>
>>>>I have 3 questions:
>>>>
>>>>1- A month ago several people recommended that I look into using the
>>>>status management approach to raising a BUS2009 event (purchase
>>>>requisitions). At the time I had already solved our problem by
>>>>calling a workflow API from a custom program. Therefore, I put the
>>>>e-mail aside.
>>>>
>>>>MIT now has need to raise yet another BUS2009 event. I'd like to
>> >>avoid the custom code route because this time we don't have a
>>>>reasonable place to put the code.
>>>>
>>>>I took a look at status management and did not see any status events
>>>>or status object types for purchasing. Am I missing something?
>>>>
>>>>=========
>>>>
>>>>2- The book "Practical Workflow for SAP" mentions that I can learn
>>>>more about raising events upon status changes from the tutorial
>>>>available in the SAP library help documentation. I can not find this
>>>>tutorial. Does anyone know where it is? We are on version 4.6c.
>>>>
>>>>=========
>>>>
>>>>3- There are actually two events we'd like to raise. If a cost
>>>>collector (cost center, internal order, wbs) changes, we'd like
>>>>"significantlyChanged" and "releaseStepCreated" to be raised. All of
>>>>our approvals are done at cost collector level and we just discovered
>>>>(after how many years in production?) that our workflow completely
>>>>ignores any change to cost collector unless the release strategy
>>>>changes. This means that someone in the School of Engineering can
>>> >accidentally approve an expense for the School of Humanities without
>>>>even realizing it! Does anyone see any pitfalls involved with raising
>>>>these two events via a non-standard trigger?
>>>>
>>>>Thanks,
>>>>
>>>>Carolyn
>>>>
>>>>
>>>>--
>>>>
>>>>"Imagine there's no heaven, it's easy if you try, no hell below us,
>>>>above us only sky, Imagine all the people, living for today." John
>>>>Lennon - Imagine
>>>>
>>>>Carolyn Fuller M.I.T.
>>>>fuller at mit.edu Financial Systems Services
>>>>http://www.mit.edu/people/fuller/ Senior Analyst/ Programmer Peer
>>>>Leader
>>>>fax (617) 253-9661 voice (617) 253-6213
>>>>W92-210
>>>
>>>
>>>--
>>>
>>>"Imagine there's no heaven, it's easy if you try, no hell below us,
>>>above us only sky, Imagine all the people, living for today." John
>>>Lennon - Imagine
>>>
>>>Carolyn Fuller M.I.T.
>>>fuller at mit.edu Financial Systems Services
>>>http://www.mit.edu/people/fuller/ Senior Analyst/ Programmer Peer
>>>Leader
>>>fax (617) 253-9661 voice (617) 253-6213
>>>W92-210
>>
>>
>>--
>>
>>"Imagine there's no heaven, it's easy if you try, no hell below us,
>>above us only sky, Imagine all the people, living for today." John
>>Lennon - Imagine
>>
>>Carolyn Fuller M.I.T.
>>fuller at mit.edu Financial Systems Services
>>http://www.mit.edu/people/fuller/ Senior Analyst/ Programmer Peer
>>Leader
>>fax (617) 253-9661 voice (617) 253-6213
>>W92-210
>
>
>--
>
>"Imagine there's no heaven, it's easy if you try, no hell below us,
>above us only sky, Imagine all the people, living for today." John
>Lennon - Imagine
>
>Carolyn Fuller M.I.T.
>fuller at mit.edu Financial Systems Services
>http://www.mit.edu/people/fuller/ Senior Analyst/ Programmer Peer Leader
>fax (617) 253-9661 voice (617) 253-6213
>W92-210
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
More information about the SAP-WUG
mailing list