Approver preview for subworkflows

[Griffiths, Mark]

N-step badi comes in in EBP 4.0 I think.

If you are in 3.5 you are much more restricted with your design. As I
understand it you will need to create workflows based on the one/two
step type workflows and use start conditions to decide which one to
start. If you want to use the Approval Preview you may need to
re-evaluate your processes.

Regards,

Mark

SAP UK Consulting.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Raju Omkaram
Sent: 13 December 2004 20:37
To: SAP Workflow Users' Group
Subject: Re: Approver preview for subworkflows


Hi Mark and Miguel,

Thanks for your feedback. I forgot to mention that I am on EBP3.5 and
there is no n-step BADI available here. Am I missing a SP for the
N-step BADI?

Please advise.

Thanks again


On Fri, 10 Dec 2004 10:36:46 -0000, Adao-Cruz, Miguel
<miguel.adao-cruz at capgemini.com> wrote:
> 
> Hi Raju and Mark,
> 
> I definitely agree with Mark, I recommend you to use the n-step BADI.
I used
> it in EBP4 and it went quite straight forward, SAP even wrote a code
sample
> in the BADI.
> Implementing everything with ad-hoc workflows can quickly become a
> nightmare.
> 
> Regards,
> 
> Miguel.
> 
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On
Behalf Of
> Griffiths, Mark
> Sent: 10 December 2004 10:23
> To: SAP Workflow Users' Group
> Subject: RE: Approver preview for subworkflows
> 
> Hi Raju,
> 
> You are very limited in your workflow design if you want to use the
> approval preview. Subflows will be shown but only if you strictly
follow
> design techniques. You have a number of options:
> 
> 1. Use the classic EBP workflow approach of using AdHoc agents. The
> workflow needs to be fairly procedural and you decide which one to
start
> with start conditions.  Problem with this is that you almost need a
> workflow for each condition (a problem if you have 15 different
process
> flows).
> 2. Use the n-step BADI style approach where you take the complexity
out
> of your workflow design, and put it in ABAP code (the BADI) which then
> returns all your approvers in a table. Depending on your release the
> approvers are then processed in sequence using a loop (EBP4), or in
EBP5
> (SRM 4, SRM Server 5) you can use the BADI to create parallel sections
> too.  If you use this approach and change your subflow watch out as
the
> step which calls the subflow needs to have a name value pair (
> sap.bc.bmt.wfm.groups / Dynamic loop ) maintained on the Properties
tab
> otherwise it won't appear in the preview.
> 
> So in summary, although subflows are displayed, you are VERY limited
on
> your design options and must design your workflow very differently to
> normal.
> 
> Kind Regards,
> 
> Mark
> 
> SAP UK
> 
> -----Original Message-----
> From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On
Behalf
> Of Raju Omkaram
> Sent: 10 December 2004 00:22
> To: SAP-WUG at MIT.EDU
> Subject: Approver preview for subworkflows
> 
> Hi,
> 
> I have customized Shopping cart approval workflow. Due to its
> cimplexity, I had to include three subworkflows. When I click,
> approver preview I see only the three sub workflow process but not
> respective approvers within the sub workflows.
> 
> Questions:
> 1. Does Approver preview for a workflow which has subworkflows?
> 2. If it does, What else I need to do to make it work?
> 
> Any help is highly appreciated.
> 
> Thanks
> Raju
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is intended
only for the person to whom it is addressed. If you are not the intended
recipient,  you are not authorized to read, print, retain, copy,
disseminate,  distribute, or use this message or any part thereof. If
you receive this  message in error, please notify the sender immediately
and delete all  copies of this message.
> 
> 
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug