to repair or not to repair

[Verschuijl, Tan]

Hi everyone,

If I understand well, some of us prefer modifying the SAP standard whereas
others prefer copying the standard...
Tell me if I am wrong making assumptions below:

If one reuses the standard:
* repair flag will be set if more changes are made than possible via
SWDD_CONFIG
* no 'old' standard SAP versions will remain visible/usable

If one copies the standard:
* possibly many tasks will need to be copied in order to be sure not to
modify accidentally the SAP standard task
* no warning from SAP whenever a workflow (or business object method) is
upgraded?
* more flexibility activating/deactivating; especially when container
elements need to be changed (incompatible change - see note 125400) one need
to create a competely new flow by copying the original one.

Any other assumptions in order to come to a conclusion?

Stan.


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Mark Pyc
Sent: woensdag, februari 02, 2005 14:22
To: sap-wug at mit.edu
Subject: RE: to repair or not to repair


G'day Stan,

Almost never is it necessary to repair anything related to Workflow. Because

of the flexible event linkage it is easy to deactivate the standard Workflow

linkage and activate the linkage for your new process. There is even some 
degree of change possible via Workflow Customizing, but most of the time it 
is easier to simply copy and extend your own version.

Have fun,
Mark

From: "Verschuijl, Tan" <Tan.Verschuijl at pmintl.com>
Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
To: "'sap-wug at mit.edu'" <sap-wug at mit.edu>
Subject: to repair or not to repair
Date: Wed, 2 Feb 2005 14:04:08 +0100

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.

_______________________________________________
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