<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2>Hi John,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2> Pls check if changed event is getting raised. If it
is raised, then your requirement will be fulfilled.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2>Regds,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254542808-05092007><FONT face=Arial
color=#0000ff size=2>Akshay</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>John A
Haworth<BR><B>Sent:</B> Wednesday, September 05, 2007 1:27 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: SRM n-step approval for PO
workflow<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>Hi</FONT> <BR><BR><FONT
face=sans-serif size=2>Thanks for the advice on the BADI.</FONT> <BR><BR><FONT
face=sans-serif size=2>I have another issue that someone may be able to advise
on. The workflow is being triggered ok, but if a PO is 'Ready for Approval' and
I make a change to the PO i.e. change quantity or value, I expected the initial
workflow/workitem would be 'logically deleted' and a new workflow created, this
is not happening.</FONT> <BR><BR><FONT face=sans-serif size=2>John<BR><BR>CSC
Computer Sciences Limited<BR>Registered Office: Royal Pavilion, Wellesley Road,
Aldershot, Hampshire, GU11 1PZ, UK<BR>Registered in England No:
0963578<BR><BR>----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>This
is a PRIVATE message. If you are not the intended recipient, please delete
without copying and kindly advise us by e-mail of the mistake in delivery.
<BR>NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement or
government initiative expressly permitting the use of e-mail for such
purpose.<BR>----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"Susan R. Keohan"
<keohan@ll.mit.edu></B> </FONT><BR><FONT face=sans-serif size=1>Sent
by: sap-wug-bounces@mit.edu</FONT>
<P><FONT face=sans-serif size=1>09/04/07 03:17 PM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif size=1>"SAP Workflow Users' Group"
<sap-wug@mit.edu></FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>Re: SRM n-step approval for PO
workflow</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT
size=2><TT>Yes John. But you need to insert your own code.<BR><BR>Have
fun!<BR>Sue<BR><BR>John A Haworth wrote:<BR>> Thanks for the explanation. So
if I create a z.... named badi and activate <BR>> it, it will automatically
be picked up from the NextDynamicApproverGet <BR>> method?<BR>> <BR>>
John<BR>> <BR>> CSC Computer Sciences Limited<BR>> Registered Office:
Royal Pavilion, Wellesley Road, Aldershot, Hampshire, <BR>> GU11 1PZ,
UK<BR>> Registered in England No: 0963578<BR>> <BR>>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
This is a PRIVATE message. If you are not the intended recipient, please
<BR>> delete without copying and kindly advise us by e-mail of the mistake in
<BR>> delivery. <BR>> NOTE: Regardless of content, this e-mail shall not
operate to bind CSC to <BR>> any order or other contract unless pursuant to
explicit written agreement <BR>> or government initiative expressly
permitting the use of e-mail for such <BR>> purpose.<BR>>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>
<BR>> <BR>> <BR>> <BR>> "Susan R. Keohan" <keohan@ll.mit.edu>
<BR>> Sent by: sap-wug-bounces@mit.edu<BR>> 09/04/07 02:07 PM<BR>>
Please respond to<BR>> "SAP Workflow Users' Group"
<sap-wug@mit.edu><BR>> <BR>> <BR>> To<BR>> "SAP Workflow
Users' Group" <sap-wug@mit.edu><BR>> cc<BR>> <BR>>
Subject<BR>> Re: SRM n-step approval for PO workflow<BR>> <BR>>
<BR>> <BR>> <BR>> <BR>> <BR>> Hi John,<BR>> <BR>> The BADI
is called from within BUS4101, method NextDynamicApproverGet, <BR>> FM
BBP_WFL_DIN_APPR_BY_RULE_GET, BADI Definition = BBP_WFL_APPROV_BADI. <BR>>
interface = IF_EX_BBP_WFL_APPROV_BADI. So when you create your BADI
<BR>> implementation, ultimately, it will be called by BUS4101, <BR>>
NextDynamicApproverGet. When I was testing this functionality out, I
<BR>> just activated the BADI and put my own code in. There are several
<BR>> examples:<BR>> <BR>> SAP_APP_BADI_EXAMPL3
Example Implementation with Value Limit <BR>> Approval
for PO<BR>> SAP_APP_BADI_EXAMPLE
Example of an Implementation of this BADI<BR>> SAP_LIA_BADI_EXMPL_2
Example for BADI Implementation in Line
<BR>> Item Approval<BR>> SAP_LIA_BADI_EX_SIMP
Simple Example for BADI Version for Item <BR>> Approval<BR>>
<BR>> I didn't have much luck using the standard SAP workflows, but modelled
<BR>> ours on them. So we do not use the BADI, per se.<BR>> <BR>>
John A Haworth wrote:<BR>>> Hi<BR>>><BR>>> Just started to
look at this SRM workflow (WS14000145) for n step PO <BR>>>
approval.<BR>>><BR>>> Just need a couple of pointers, if a new BADI
is created, where is <BR>> called <BR>>> from? does the standard one
pick up the approval limits from the org <BR>>> chart? The org chart has
been created with the approvers limits and <BR>>> managers, the first
approver is informed, but a subsequent change and <BR>>> value increase to
the PO doesnt cancel the first workitem and create a <BR>> new <BR>>>
one.<BR>>><BR>>> Any info would be good.<BR>>><BR>>>
Thanks<BR>>><BR>>> CSC Computer Sciences Limited<BR>>>
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,
<BR>> <BR>>> GU11 1PZ, UK<BR>>> Registered in England No:
0963578<BR>>><BR>>><BR>>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>>
This is a PRIVATE message. If you are not the intended recipient, please
<BR>> <BR>>> delete without copying and kindly advise us by e-mail of
the mistake in <BR>>> delivery. <BR>>> NOTE: Regardless of content,
this e-mail shall not operate to bind CSC <BR>> to <BR>>> any order or
other contract unless pursuant to explicit written <BR>> agreement
<BR>>> or government initiative expressly permitting the use of e-mail for
such <BR>> <BR>>> purpose.<BR>>><BR>>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<BR>>><BR>>><BR>>>
------------------------------------------------------------------------<BR>>><BR>>>
_______________________________________________<BR>>> SAP-WUG mailing
list<BR>>> SAP-WUG@mit.edu<BR>>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>>
------------------------------------------------------------------------<BR>>
<BR>> _______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>>
http://mailman.mit.edu/mailman/listinfo/sap-wug<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>Phone: 781-981-3561<BR>Fax:
781-981-1607<BR>keohan@ll.mit.edu<BR>_______________________________________________<BR>SAP-WUG
mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></TT></FONT><BR></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>