AW: Event CREATED for BUS2054 raised when WBS is changed ?

[Becker Stephan (extern)]

Susan,
 
have your ABAPer debug the transaction that raises the event, it is =
probably
raised hard-coded (like BUS2032.Created and .Changed), and it may just =
be
that the trigger isn't 100% kosher.. just like the Purchase Order =
Changed
event doesn't get triggered on address changes or the Sales Order =
Created
event gets triggered when contracts, quotations, and the like are =
created..
SAP seem to be short staffed in that area and are not offering remedies =
but
rather admit to "functional gaps" after weeks or months of refusing to
acknowledge the existence of the problem in the first place..
 
A CFM would probably help as a workaround (effective for the sales =
order
example above), sometimes it's a bit more complex (e.g. the PO example
given, only works efficiently via a second event and a bit of
thought-through code..)
 
Hth,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Susan R. Keohan [mailto:skeohan at mit.edu]
Gesendet: Mittwoch, 3. Juli 2002 15:28
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Event CREATED for BUS2054 raised when WBS is changed ?
 
 
Hello WF-ers,
 
I have a workflow I want triggered when a WBS (BUS2054) is created.
This works fine, except that when a WBS is changed, the event WBS
CREATED also gets raised !!  I have looked at transactions SWED, SWED,
and SCDO and can't find anything that would trigger this event.  The
changes are being done by a background job and the ABAPer swears he is
not raising the event manually.
 
Any hints on where I can go to ensure that the event BUS2054 CREATED
gets raised only when one is really created ?
 
Thanks in advance,
Sue