We are designing our "to-be" processes for SAP R/3, apparently without Workflow and without ESS for a large city with about 28 000 employees over a wide geographic area. We figure the paper chase in administering payroll and HR across a wide area will be difficult without some kind of Workflow. Is there any point in designing business process now with Workflow to avoid later work? And is Workflow not standard with SAP/R3?
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
I believe that SAP Workflow should be integral part of any implementation from the beginning. I have seen clients pay for very expensive developments in order to implement complex business processes using standard development techniques (reports, custom dialogs, etc). The tragic part of it is that these processes could have been more efficiently and cheaply using SAP Workflow. The solution usually is quite complex and hence expensive to run and maintain. Unfortunately, neither the client nor the consultants knew better. I would strongly urge you to implement Workflow as part of your initial build. It ensures that clients begin reaping the rewards of their investment and hence increase their ROI.
Workflow is standard with R/3. SAP provides a high number of Workflow Templates out of the box. Rarely are these templates a 'perfect fit' and usually require some changes to fit the particular client's requirements.
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
Join the conversationComment
Share
Comments
Results
Contribute to the conversation