Event type linkage de-actived

[Kjetil Kilhavn]

Couldn't agree more! Never use deactivation as the default.
 
Perhaps there is another case where it could be useful (on the specific event). I have never really given this much thought previously.
 
I don't have any experience with this myself, but assume there is a high-volume application where all will fail if one fails (i.e. failure is not depending on event-specific data), e.g. because a required connection to another system is down. Wouldn't that mean a lot of administration (restarting or logical deleting) could be avoided by disabling the event linkage when it fails?
-- 
Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP
 



________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dart, Jocelyn
	Sent: 9. mai 2006 08:49
	To: SAP Workflow Users' Group
	Subject: RE: Event type linkage de-actived
	
	
	Yes fair enough - but then only on that specific event - it should never be the default setting in SWEQADM. 
	 

	Regards, 
	Jocelyn Dart 
	Senior Consultant 
	SAP Australia Pty Ltd. 
	Level 1/168 Walker St. 
	North Sydney 
	NSW, 2060 
	Australia 
	T   +61 412 390 267 
	M   + 61 412 390 267 
	E   jocelyn.dart at sap.com 
	http://www.sap.com <http://www.sap.com/>  

	
	 
________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kjetil Kilhavn
	Sent: Tuesday, 09 May 2006 4:17 PM
	To: SAP Workflow Users' Group
	Subject: RE: Event type linkage de-actived
	
	
	In the unfortunate situation where you have to process a specific event in the sequence it is generated (e.g. if you have a first come, first serve type of application), deactivating is the only sensible choice I think. It shouldn't be used unless there is no way around it.
	-- 
	Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP
	 
	
	

________________________________

		From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dart, Jocelyn
		Sent: 9. mai 2006 01:50
		To: SAP Workflow Users' Group
		Subject: RE: Event type linkage de-actived
		
		
		By the way you should always use Mark Linkage as Having Errors in production - so the bad events are captured and can be redelivered from SWEQADM. 
		 
		Deactivate linkage should not be used at all in my opininon.
		 
		Do not change linkage is handy for development where you don't really care about failures. 
		 

		Regards, 
		Jocelyn Dart 
		Senior Consultant 
		SAP Australia Pty Ltd. 
		Level 1/168 Walker St. 
		North Sydney 
		NSW, 2060 
		Australia 
		T   +61 412 390 267 
		M   + 61 412 390 267 
		E   jocelyn.dart at sap.com 
		http://www.sap.com <http://www.sap.com/>  

		 
________________________________

		From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Ribbens, Andy
		Sent: Monday, 08 May 2006 9:39 PM
		To: SAP Workflow Users' Group
		Subject: Event type linkage de-actived
		
		

		Hi all, 

		We came to the conclusion that a certain workflow event is not triggered anymore. 
		In the workflow log we saw the message 'Deactivated' for an own created event 'COMPLETEINVOICESCANNINGMM' of object 'BUS2081' . 

		In the eventtype linkage transaction SWETYPV, I see that the 'type linkage active' flag is not marked anymore. 

		Is there anybody who knows how the de-activation is triggered and how we can solve this in the future ? 

		Wkr, 
		Andy 


		------------------------------ 
		Ribbens Andy 
		Software Engineer 
		Tel : + 32 (0)53/73.38.21   
		GSM: + 32 478/78.08.19 
		E-mail: Andy.Ribbens at Tateandlyle.com 
		------------------------------ 

	 



-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060509/0c5344d7/attachment.htm