to repair or not to repair

[Dart, Jocelyn]

By the way, Stan, one of the reasons for copying is that (unlike
programs) there's no easy equivalent of the modification assistant for
workflows.  
Jocelyn 


________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Verschuijl, Tan
	Sent: Thursday,3 February 2005 12:04 AM
	To: 'sap-wug at mit.edu'
	Subject: to repair or not to repair
	
	
	Hi everyone,
	 
	I just subscribed to this mailing list and tried to find
information within the archive but was not succesful (yet).
	 
	I am unsure when to make a copy from a workflow and/or task.  
	The SAP workflow book (Practical workflow for SAP) encourages
the reader to use and modify standard SAP workflows. It does not mention
to which extend a Standard SAP workflow should be changed. As a
developer I prefer to make a copy. Are there any reasons to repair
(change agent assigment rule, bindings) a standard SAP task/workflow? If
a make a copy the functional consultant will probably not see the
workflow in use anymore via SPRO? 
	 
	If one changes a workflow (and the repair flag is set in object
attributes) how does one find out that SAP made an improvement on an
existing workflow/task? Is version 000 automatically overwritten by SAP?
	 
	Best regards,
	Stan. 
	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050203/9569f5a2/attachment.htm