<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: n-Step Approval workflow (BADI workflow for PO)</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText49611 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>
<DIV id=idOWAReplyText85049 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Sue,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Thanks for your valuable
inputs.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>I was under assumption that n-step BADI
workflow will work only with std SAP delivered templates.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>
<DIV dir=ltr><FONT face=Arial size=2>Just need one more input to check whether
my assumption is correct or not.</FONT></DIV>
<DIV dir=ltr>( To elaborate more, aim is to implement the BADI, but with custom
worklfow i.e copy of std SAP template)</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Could you suggest some imp points which you mentioned that "should
be taken care".</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Thanks in advance.</DIV>
<DIV dir=ltr>Regds,</DIV>
<DIV dir=ltr>Akshay Bhagwat</DIV></FONT></DIV></DIV></FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu on behalf of Susan
Keohan<BR><B>Sent:</B> Wed 3/28/2007 5:53 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> Re: n-Step Approval workflow (BADI workflow for
PO)<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi Akshay,<BR><BR>We copied the SAP-delivered templates for the
N-step workflows, and<BR>substituted our own approval routing method in the
place of the BUS4101<BR>NEXTDYNAMICAPPROVERGET. We were able to utilize
this approach for<BR>Shopping Carts, POs, Bids and Contracts. One of the
tricky areas was<BR>the standard templates have a value in the workflow
container (Initial<BR>Value) and this caused SRM to want the custom workflows to
have the BADI<BR>implemented. So if you have your own approval rules, and
are not<BR>implementing them in the BADI, then have a care there.<BR><BR>There
was one reason we did not go with the BADI approach. 1) To<BR>accomplish
dynamic parallel approvals was going to mean using the Item<BR>Level approvals,
and dummying up the item GUIDs - which seemed a wee bit<BR>confusing.
Otherwise, we could have just used the templates SAP delivered.<BR><BR>Good
luck,<BR>Sue<BR><BR>Kris wrote:<BR>> Hi,<BR>> <BR>> You don't have
to change the template. You can develop the approval<BR>> determination logic
in BADI. Use GET_REMAING_APPROVERS method to build<BR>> your
logic.<BR>> <BR>> Thanks<BR>><BR>> <BR>> On 3/27/07,
*akshay.bhagwat@wipro.com <<A
href="mailto:akshay.bhagwat@wipro.com">mailto:akshay.bhagwat@wipro.com</A>>*<BR>>
<akshay.bhagwat@wipro.com <<A
href="mailto:akshay.bhagwat@wipro.com">mailto:akshay.bhagwat@wipro.com</A>>
> wrote:<BR>><BR>> Hi
All,<BR>> <BR>> I
have not worked on SRM workflow area for n-step approval,
so<BR>> needed some inputs /
help.<BR>> WS14000145 is std workflow for n-step
approval.<BR>> Wanted to know that is it possible to
copy this and create a<BR>> customized workflow for
n-step approval *or* we have to use this std<BR>>
workflow only and only area we can play around is with BADI
i.e.<BR>> approval
determination?<BR>> <BR>>
Thanks in
advance.<BR>> <BR>>
Regds,<BR>> <BR>>
Akshay Bhagwat<BR>><BR>> The information contained
in this electronic message and any<BR>> attachments
to this message are intended for the exclusive use
of<BR>> the addressee(s) and may contain proprietary,
confidential or<BR>> privileged information. If you
are not the intended recipient, you<BR>> should not
disseminate, distribute or copy this e-mail.
Please<BR>> notify the sender immediately and destroy
all copies of this message<BR>> and any
attachments.<BR>><BR>> WARNING: Computer viruses
can be transmitted via email. The<BR>> recipient
should check this email and any attachments for
the<BR>> presence of viruses. The company accepts no
liability for any damage<BR>> caused by any virus
transmitted by this email.<BR>><BR>> www.wipro.com
<<A
href="http://www.wipro.com/">http://www.wipro.com/</A>><BR>><BR>><BR>>
_______________________________________________<BR>>
SAP-WUG mailing list<BR>> SAP-WUG@mit.edu <<A
href="mailto:SAP-WUG@mit.edu">mailto:SAP-WUG@mit.edu</A>><BR>>
<A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>><BR>><BR>><BR>>
------------------------------------------------------------------------<BR>><BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>> <A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>--<BR>Susan
R. Keohan<BR>SAP Workflow Developer<BR>MIT Lincoln Laboratory<BR>244 Wood
Street<BR>LI-200<BR>Lexington, MA.
02420<BR>781-981-3561<BR>keohan@ll.mit.edu<BR>_______________________________________________<BR>SAP-WUG
mailing list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></FONT></P></DIV>
</BODY>
</HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000><br>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. <br>
<br>
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.<br>
<br>
www.wipro.com<br>
</font></td></tr></table>