<br><font size=2 face="sans-serif">Dont suppose you have any sample code,
to start me off??</font>
<br>
<br><font size=2 face="sans-serif">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%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Susan R. Keohan"
<keohan@ll.mit.edu></b> </font>
<br><font size=1 face="sans-serif">Sent by: sap-wug-bounces@mit.edu</font>
<p><font size=1 face="sans-serif">09/04/07 03:17 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"SAP Workflow Users' Group" <sap-wug@mit.edu></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: SRM n-step approval for PO workflow</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></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>