Theoretical question - WF Design

[Dart, Jocelyn]

Hi Sue, 
Be careful! 

If you are talking SC item level BADI then the visibility of the
approval process is not based directly on the workflow log but rather on
certain tables held in the container of the top level work item. 

As the other BADI workflows share the same code, I would be very careful
about assuming what the approval preview will show if you change the
workflow. 


Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Susan R. Keohan
Sent: Thursday, 10 November 2005 7:58 AM
To: SAP Workflow Users' Group
Subject: Re: Theoretical question - WF Design

Hi Richard, Raju,

Thanks for the feedback, but I am talking about conditions that occur
within the workflow after a 
given approval step (who approved it, did they approve it or reject it,
where should it go from 
here, based on who they are, etc.).  Much of the approval path should be
determined by the N-step 
BAdi, but it's the deviations from the norm that I am concerned about.

We've had issues in the past with various conditions set/tested within
the methods themselves, and I 
think I am leaning towards providing as much visibility to the process
flow as possible,(via the 
workflow logs).  Although folks could also just learn how to drill into
the container and see the 
various flags and indicators there as well.

However, Raju's comments are also valid.  We have several workflows that
are 2 pages wide, by 3 
pages down.  That's why I am pinning all my hopes on the BAdi!

So many ways to skin a cat...

Happy WF-ing,
Sue

Richard Marut wrote:

> Sue,
> 
> Another option is to use a start condition. You could also code your
own
> check function module and manually add it to the type linkages table.
The
> start condition will not require an ABAP or Workflow resoucre, just
someone
> who can understand conditions. The Check FM will require ABAP but will
be
> easy to find.
> 
> Richard...
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf Of
> Susan R. Keohan
> Sent: Wednesday, November 09, 2005 11:55 AM
> To: SAP Workflow Users' Group
> Subject: Theoretical question - WF Design
> 
> 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