SRM n-step approval for PO workflow

Susan R. Keohan keohan at ll.mit.edu
Tue Sep 4 09:07:47 EDT 2007


Hi John,

The BADI is called from within BUS4101, method NextDynamicApproverGet, 
FM BBP_WFL_DIN_APPR_BY_RULE_GET, BADI Definition = BBP_WFL_APPROV_BADI. 
interface = IF_EX_BBP_WFL_APPROV_BADI.  So when you create your BADI 
implementation, ultimately, it will be called by BUS4101, 
NextDynamicApproverGet.  When I was testing this functionality out, I 
just activated the BADI and put my own code in.  There are several 
examples:

SAP_APP_BADI_EXAMPL3	Example Implementation with Value Limit Approval for PO
SAP_APP_BADI_EXAMPLE	Example of an Implementation of this BADI
SAP_LIA_BADI_EXMPL_2	Example for BADI Implementation in Line Item Approval
SAP_LIA_BADI_EX_SIMP	Simple Example for BADI Version for Item Approval

I didn't have much luck using the standard SAP workflows, but modelled 
ours on them.  So we do not use the BADI, per se.

John A Haworth wrote:
> Hi
> 
> Just started to look at this SRM workflow (WS14000145) for n step PO 
> approval.
> 
> Just need a couple of pointers, if a new BADI is created, where is called 
> from? does the standard one pick up the approval limits from the org 
> chart? The org chart has been created with the approvers limits and 
> managers, the first approver is informed, but a subsequent change and 
> value increase to the PO doesnt cancel the first workitem and create a new 
> one.
> 
> Any info would be good.
> 
> Thanks
> 
> CSC Computer Sciences Limited
> Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire, 
> GU11 1PZ, UK
> Registered in England No: 0963578
> 
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 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. 
> 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.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
Phone: 781-981-3561
Fax:   781-981-1607
keohan at ll.mit.edu



More information about the SAP-WUG mailing list