Event Triggering Twice

Bibby, David david.bibby at Linklaters.com
Mon Jan 31 06:36:52 EST 2005


Richard, Dan,
I forgot to mention in my original message that I had checked SWETYPV and there is only one entry in there.
 
However I've now have checked SWEC and found an entry in there for BUPA_BUP BUS1006 CHANGED.
In our other two systems where this problem isn't happening there is no SWEC entry.
 
I think it might be possible that our 4.0 upgrade to this system added this SWEC entry. The other two systems are still on 3.1
 
Many Thanks
David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of Getliffe, Dan
Sent: 31 January 2005 04:45
To: SAP Workflow Users' Group
Subject: RE: Event Triggering Twice


Hi David,
 
As Richard has said the first thing to do is to determine how the 2 events are being raised e.g. change documents, through the application etc.. and then determine if both event linkages are required to be active in the system.  I recently had the situation with the standard PO release workflow where one event was being raised by the application and another event was being raised via an entry in SWEC (change documents) which appeared following the application of a support package - for this particular problem there was an OSS note that recommended deactivating the event raised via change documents.  It is worth having a check on OSS and determining if any support packages have been recently applied.
 
Regards,
 
Dan.  
 

Dan Getliffe 
NetWeaver Consultant 
SAP Australia Pty. Ltd 
level 2, 441 St Kilda Road 
Melbourne VIC 3004 
T   +61 3 9862 7144 
F   +61 3 9862 7244 
M   +61 438 234 533 
E    <mailto:dan.getliffe at sap.com> dan.getliffe at sap.com 
http://www.sap.com/australia 




 


  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Richard Marut
Sent: Monday, 31 January 2005 3:05 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Event Triggering Twice



David,

 

Take a look at transaction SWETYPV for entry BUS1006.Changed and you will see two entries with active linkages. You can either disable one entry or look into why there are two active. I once ran into a situation where two entries were active because someone decided to experiment with workflow. If both entries are supposed to be active, you may want use a start condition or check function module to start them only when needed.

 

Richard...

 


  _____  


From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Bibby, David
Sent: Friday, January 28, 2005 9:55 AM
To: sap-wug at mit.edu
Subject: Event Triggering Twice

 

I have a problem with a workflow where the event triggers twice and the workflow therefore triggers twice. 

The Business Object is BUS1006 and the event is CHANGED. 

In CRM 4.0, when a Business Partner is edited in transaction BP a workflow is supposed to trigger. 

The only visible difference I can see in the two event log entries is the main program. 
One says the main program is SAPLBUPA_DIALOG_JOEL and the other event has the main program RSM13000. 

I have never seen this before. Has anyone any ideas what could be causing this ? 

Many Thanks 
David 


  _____  


This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents to anyone. All messag
es sent
to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are
not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, lost or destroyed, or contain
viruses. Anyone who communicates with us by email is taken
to accept these risks.

The contents of any email addressed to our clients are subject
to our usual terms of business; anything which does not relate
to the official business of the firm is neither given nor endorsed by it. 

The registered address of the UK partnership of Linklaters is One 
Silk Street, London, EC2Y 8HQ. Please refer to 
http://www.linklaters.com/regulation for important information on
the regulatory position of the firm.




-----------------------------------------------------------------------

This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents to anyone. All messages sent
to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are
not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, lost or destroyed, or contain
viruses. Anyone who communicates with us by email is taken
to accept these risks.

The contents of any email addressed to our clients are subject
to our usual terms of business; anything which does not relate
to the official business of the firm is neither given nor endorsed by it.  

The registered address of the UK partnership of Linklaters is One 
Silk Street, London, EC2Y 8HQ. Please refer to 
http://www.linklaters.com/regulation for important information on
the regulatory position of the firm.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050131/00b99c9f/attachment.htm


More information about the SAP-WUG mailing list