BUS2012.SignificantlyChanged vs ReleaseStepCreated in ECC5.0

[Kjetil Kilhavn]

Ooops, that was a bit embarassing....
As they say, it is the eyes that lose sight first.
-- 
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 Mark Pyc
	Sent: 10. august 2006 17:06
	To: SAP Workflow Users' Group
	Subject: Re: BUS2012.SignificantlyChanged vs ReleaseStepCreated in ECC5.0
	
	
	Thanks Tami, I appreciate you taking the time!
	 
	I thought I'd be okay using ReleaseStepCreated but you've pointed out a very important one, the deletion of all items which means a Release Step won't be created. I really need SigChgd but I've just tested and I don't get it. 
	 
	Looks like this might be one for OSS after all.
	 
	G'day Kjetil, but nope, my own advice is no use to me. No surprises there.
	 
	Have fun,
	Mark
	
	 
	On 8/10/06, tamara.elliott at kodak.com <tamara.elliott at kodak.com > wrote: 


		Marc, 
		
		In my testing this is what I found with SignificantlyChanged (release 4.7).  It is raised when: 
		
		1. the PO price is changed so that it crosses release code levels (SignificantlyChanged is what completes the existing workflow, and ReleaseStepCreated kicks off the new workflow) 
		
		2.  a release has been rejected (again to complete the existing workflow) 
		
		3.  a release has been cancelled (via transaction ME29N) 
		
		4.  the PO has been cancelled (all of the line items within the PO are deleted) 
		
		I mainly found that the SignificantlyChanged event is used to complete whatever workflow is currently running. 
		
		Tami Elliott
		Eastman Kodak
		
		
		
		
		
"Mark Pyc" <mark.pyc at gmail.com> 
Sent by: sap-wug-bounces at mit.edu 

08/10/2006 08:37 AM 
Please respond to
"SAP Workflow Users' Group" < sap-wug at mit.edu <mailto:sap-wug at mit.edu> >


To
WUG <sap-wug at mit.edu> 
cc
Subject
BUS2012.SignificantlyChanged vs ReleaseStepCreated in ECC5.0	

		


		



		 

	
	G'day Wuggers, 
	  
	I'm confused. 
	  
	When does BUS2012.SignificantlyChanged get raised? I was under the impression that when a change occured such that a released doc is blocked again the event SignificantlyChanged would be raised (this is certainly what the help suggests) however I only get the event ReleaseStepCreated. 
	  
	To begin with I was surprised because I had my heart set on getting a SignificantlyChanged. Now that I think about it I'm not sure that it matters since I can react to the ReleaseStepCreated event. 
	  
	But then I wonder why the SignificantlyChanged event exists. 
	  
	What am I missing? 
	  
	I should point out that there is only a single stage Release Strategy with a single code. 
	  
	Can anyone provide some insight for me?? 
	  
	Many thanks, 
	
	Mark_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	
	 

	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	
	
	
	



-------------------------------------------------------------------
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/20060811/0045da0d/attachment.htm