WORKFLOW BEST PRACTICES

Tue May 9 10:34:09 EDT 2006

Mark & Larry,
This is a very interesting conversation point which we have debated in-house as well.  There are certainly two aspects to a workflow developer.  The first skill set is that of the process analyst/ developer.  Understanding the business process and the "big picture" is essential to delivering a workflow that will benefit the business.  Being able to communicate with non-technical language to the business owners is often neccessary.  In those instances where this can be accompished with SAP delivered workflow tools and BOT's, the cost to develop and support can be minimal and does not require any ABAP skills.  
This second skill is that of the ABAP programmer/ developer.  In the frequent circumstances where the standard delivered workflow tools and BOT's are not sufficient to meet the business needs, a talented programmer is needed.
If you are fortunate to have all of those skills in one individual, then in my humble opinion, you have the dream workflow developer.
(And by reading the emails in this group I can see that there are several of these experts out there.)  However, it is possible to have those two skills reside in 2 different people, or even in 2 different departments in a large global corporation.  
Best of luck to all of us in our various workflow roles.
Cheers,
Sherie
  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mark Pyc
Sent: Tuesday, May 09, 2006 10:09 AM
To: SAP Workflow Users' Group
Subject: Re: WORKFLOW BEST PRACTICES

I guess this gets into the world of demarcation disputes. If you have a situation where the WF developer creates a method as a wrapper for a function but asks a more qualified developer to deliver that function than the statement could hold true. It really depends on how many people you have to change the Workflow lightbulb. 

On the whole though I believe that the inherent logic of a Workflow and the common need to pull apart the standard system (looking for event trigger points mainly) requires a strong developer regardless of how much code they cut. 

Have fun,
Mark

On 5/9/06, lianghuan.x.hu at accenture.com <lianghuan.x.hu at accenture.com > wrote: 

	Sherie:

	Thanks for sharing the document.  But I do not agree with one point under "Workflow and ABAP" on Slide 9 which says that a workflow developer needs only " light ABAP knowledge". In fact, a workflow developer is an ABAP developer with additional workflow skills. A workflow developer has to write all kinds of ABAP code that regular ABAP developer does, the only difference is that he has to put his code behind the business object types. The word "light" is both unfair and misleading. 

	Thanks,
	Larry Hu

	n

  _____  

	From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu> ] On Behalf Of Munday,Sherie J.
	Sent: Monday, May 08, 2006 2:21 PM
	To: SAP Workflow Users' Group
	Subject: RE: WORKFLOW BEST PRACTICES

	Anjan,
	This attachment is a high level summary that we did called Workflow 101.  It does not necessarily cover best practices, but you might find it useful.  The most important tip I would give anyone starting to develop workflows is to make sure that the business process is well defined before you design the workflow.  If the process is not defined you will waste time and effort chasing a moving target and the scope creep will be unbelievable!! 
	Best of Luck,
	Sherie

  _____  

	From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu> ] On Behalf Of Rakshit, Anjan (CA - Toronto)
	Sent: Monday, May 08, 2006 12:34 PM
	To: sap-wug at mit.edu
	Subject: WORKFLOW BEST PRACTICES

	Our client is requesting information about the high-level policies, guiding principles, and governance for Workflow used by other SAP users - particularly any high-tech manufacturing organizations.  The client is approaching initial design and configuration of SAP and feel they need an overall governance strategy for the implementation, change management, and on-going maintenance of Workflow. 

	If anyone has a governance document, best practices document or tips and tricks on workflow design for SAP, it would be greatly appreciated. 

	Thanks and regards

	Anjan Rakshit 

  _____  

	*******************************************************************
	*******************
	Confidentiality Warning: This message and any attachments are
	intended only for the use of the intended recipient(s), are 
	confidential, and may be privileged. If you are not the intended
	recipient, you are hereby notified that any review, retransmission,
	conversion to hard copy, copying, circulation or other use of this
	message and any attachments is strictly prohibited. If you are not 
	the intended recipient, please notify the sender immediately by
	return e-mail, and delete this message and any attachments from
	your system. Thank you.

	Information confidentielle: Le présent message, ainsi que tout 
	fichier qui y est joint, est envoyé à l'intention exclusive de
	son ou de ses destinataires; il est de nature confidentielle et
	peut constituer une information privilégiée. Nous avertissons
	toute personne autre que le destinataire prévu que tout examen, 
	réacheminement, impression, copie, distribution ou autre
	utilisation de ce message et de tout fichier qui y est joint est
	strictement interdit. Si vous n'êtes pas le destinataire prévu,
	veuillez en aviser immédiatement l'expéditeur par retour de 
	courriel et supprimer ce message et tout document joint de votre
	système. Merci.
	*******************************************************************
	*******************

	This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. 

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

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