Appropriation Request

Michael Pokraka workflow at quirky.me.uk
Wed Sep 22 12:37:17 EDT 2004


Hi Hal,
You're always better off writing your own. Period.
 
It gives you that opportunity to adjust it to your needs and add those
little tweaks and bells that would be nice to have. Also it is far easier=
 to
change when someone does come along with another additional requirement -
there's no need to make these additional items fit with the SAP flow.
 
There have been plenty discussions on the topic, and many would agree tha=
t
most SAP flows are best used as a starting point - an idea if you wish - =
for
developing your own flow.
 
Cheers
Mike
 
Fairless, Hal wrote:
> We are considering the implementation of Appropriation Requests Approva=
l
> (WS00300022, IM_WF_APP, Approve appropriation request) but have found
> that BUS2104 is obsolete and has been replace by BUS2204.  However,
> according to note 377117, WS00300022 has NOT been changed to use the ne=
w
> object, but that it is still OK to use BUS2104 for the workflow.  Also,
> due to our 'unique' approval process, we would need to extend the base
> object to incorporate our approval process.  Since we would be extendin=
g
> either object my question is:
> Would we be better off to use BUS2204 and develop our own workflow, or
> should we use BUS2104 and modify the existing workflow? Pro's and Con's
> would be appreciated.
>
> Thanks
>
> Hal Fairless
> Pacificorp
>
> -----------------------------------------------------------------------=
-------
>
> This email is confidential and may be legally privileged.
>
> It is intended solely for the addressee. Access to this email by anyone
> else, unless expressly approved by the sender or an authorized addresse=
e, is
> unauthorized.
>
> If you are not the intended recipient, any disclosure, copying, distrib=
ution
> or any action omitted or taken in reliance on it, is prohibited and may=
 be
> unlawful. If you believe that you have received this email in error, pl=
ease
> contact the sender, delete this e-mail and destroy all copies.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
 


More information about the SAP-WUG mailing list