Notification status event using BSVW?

[Lante, Jason (ETSA)]

Hi SAP Workflow users,
 
I am new to this forum so I apologise if this question has been answered
previously.  Also, my searches into the archives were unsuccessful.
 
My problem is that a notification status change is not raising an event.
 
So far, I have:
1) Created the event on business object ZBUS2080, Service Notification,
which is inherited by BUS2080
2) Created a link to that event using status management, BSVW, using
customer settings.
        StatusOT = QMI
        BusinessOT = BUS2080
        Status Restrictions are based on a schema (Z_NOT_CC) that we are
using and includes status SUBM, SCRQ, FSRQ & RFAP.
3) I have switched the event trace on... SWELS
4) I then change a notification that is using the same status schema
(Z_NOT_CC).
5) Looking in the Event Trace, SWEL, I cannot see that the event is
being raised.
 
I have also created a workflow task to update a temporary table when it
is triggered but this is not occurring.  The event appears to work okay
when I perform a simulate event, SWU0, and a create event, SWUE, is
updating the temporary table correctly.
 
Just as a side note, we have a similar workflow setup for a different
schema (Z_NOT_CS) for status RFAP and this is creating events perfectly.
 
My problem is that the event is not being raised when a notification is
actually changed to one of the linked events.
 

Regards,

Jason Lante
SAP Analyst Programmer
  
ETSA Utilities
(   08 8404 5056
+ lante.jason at etsa.com.au <mailto:lante.jason at etsa.com.au> 
 P please consider the environment before printing this email 

 


**********************************************************************
This email and any file attachments are confidential. 
If you have received this email in error please notify the sender and 
delete the email. 
You should note the contents of the email do not necessarily represent 
the views of ETSA Utilities, nor can we guarantee that the email is 
free of any malicious code. If you have any doubts about the source or 
authenticity of the email, please contact us on 13 12 61.
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090923/f9d7bdfe/attachment.htm