WORKFLOW BEST PRACTICES

Tue May 9 10:57:03 EDT 2006

Gavin and Mark:

Thanks for your comments. 

I did not know some projects trying to build up workflows using workflow developers doing the BO shell only to call  functions and ABAP developers actually coding those functions. Situations like these highlight the need for a workflow developer to have serious ABAP skills. 

And let's remember, the ABAP code behind BO is not the only thing a workflow developer has to work on. Sometimes he has to code the right event to trigger the workflow. And some companies want their workflow developers to code or maintain BSP code. ...

There is a big misunderstanding among project leaders that a workflow developer only plays with those graphic flowcharts. 

Thanks,
Larry

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

Hi Larry,

It's an interesting question - I think a workflow developer who doesn't know ABAP is like a mountaineer without a rope. In the simplest cases it won't be needed (e.g. a simple approvals workflow) but for anything a bit more complicated it will be.

At my project the client wanted to train two resources in "Workflow without ABAP", and the ABAP parts of their developments would be outsourced to an 'ABAP-er'. They have now seen that this approach doesn't really work and the resources are going to learn ABAP. At design time there are problems as the workflow developer doesn't know what is possible with ABAP and may not know how to specify the ABAP requirements. Also an 'ABAP-er' without workflow experience won't know about containers and the swc* macros, nor the function of a agent determination rule, the BOR, the SAP_WAPI function modules, etc.

I would be interested to know if other people have experience of workflow development without ABAP.

Regards,
Gavin

2006/5/9, lianghuan.x.hu at accenture.com <lianghuan.x.hu at accenture.com>:
>
> 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] 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] 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
>
>
>

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

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.