Theoretical question - WF Design

[Raju Omkaram]

Susan,
 I ran into same issue few months back. I prefer putting lot of code in the
method than complicating the workflow. If there is a change in the business
rule, provided ABAP best practice is followed, it is less effort to change
than the WF itself. If there is change or bug in the workflow branch, it is
less effort to test that piece alone leaving the complicated ABAP code
alone.
 I created a WF similar to N-step BADI, since it was not available in the
version of SRM I was working on, it took me twice as much time to
troubleshoot the complicated WF conditions and WF ran into 3 full screens
down and two screens wide.
 Personally, I vote for putting conditions in business object method rather
than in WF.
 Regards,
Raju

 On 11/9/05, Susan R. Keohan <keohan at ll.mit.edu> wrote:
>
> Hello all,
>
> I am in the process of designing workflows for SRM 5.0 (Shopping Cart
> Release - using N-step BAdi,
> PO, etc.). My organization is very thin when it comes to workflow
> expertise. Therefore, I ask the
> following:
>
> Is it better to put conditions, branching, etc in the workflow itself,
> which exposes the conditions,
> but also complicates the flow, and would require a WF person to
> modify/maintain, or
>
> put a lot of effort into the underlying ABAP, the theory being that it
> would be easier to find an
> ABAPer who can maintain/modify the code. The drawback, of course, is that
> the conditions are not so
> visible.
>
> There's no right or wrong answer... just food for thought.
>
> Happy WF-ing,
> Sue
> --
> Susan R. Keohan
> SAP Workflow Developer
> MIT Lincoln Laboratory
> 244 Wood Street
> LI-200
> Lexington, MA. 02420
> 781-981-3561
> keohan at ll.mit.edu
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051109/6dbfa29b/attachment.htm