<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Duration of work flow projects</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2 FACE=3D"Arial">Stefan,</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">We have been using SAP WF for PRs and =
Invoices since mid last year. Please note:</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">1. Get an experienced SAP ABAP =
programmer on-board real quick, not alternative!!</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">2. Make sure that your ABAP guy is =
trained in SAP Work Flow. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">3. The implementation time would vary =
depending upon the skill of your ABAP guy, after blue print has been =
established, a month is an O.K estimate. If you include testing, =
go-live etc a good estimate is 1.5 - 2 months for each process (like =
PR, Invoices etc).</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">4. We are using all 8 release levels =
from release strategy, we also use SAPMAPI 4.5B. SAPMAPI 4.5B is not =
stable!!! You will be in support mode constantly. Users will be calling =
all the time compalining that they can not receive e-mails in SAPMAPI =
inbox.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">5. SAPMAPI is a performance haug, you =
would need to understand your systems requirements to make sure that =
you still get optimal performance.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Good luck.</FONT>
</P>
<BR>
</BODY>
</HTML>