How to organize staff for Workflow development

How to organize staff for Workflow development

We are in the process of automating the creation of a material using Workflow. Since this is the first attempt at using Workflow, I have been asked to determine how other companies organize their staff as it relates to workflow development. Generally speaking does the Business analyst (configuration) determine and/or define the process, then there is a Workflow developer to create the workflow and if necessary an ABAP'er for any custom code? Or would one person (i.e. Business Analyst) determine the process as well as create the workflow? I am thinking the latter is the better way. What have you seen in your experiences with other companies? Thanks for your input.


    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The best results are definitely achieved by having the Business Analyst concentrate on the requirements and how they can be achieved in SAP and allowing the technical specialists determine the best way of implementing the Workflow. A lot of times Workflows are unnecessarily complicated or inefficient because they have been designed and built by people who do not have a technical background. The best results are definitely achieved with both a functional and a technical resource. I don't see a need for a separate ABAP'er as I believe that a Workflow developer should also be an ABAP'er.

If you have any more specific questions please do not hesitate to contact me at araskin@3i-consulting.com.


This was first published in May 2002