SRM approval BADI - n Step approval

Wayne Rix wayneri at absa.co.za
Fri Jul 14 09:30:45 EDT 2006


Hello all,
 
This is my first post here so please be patient if my question is completely
silly.
 
We have implemented the standard n-step approval badi here for determining
our shopping cart and purchase order approvers using the standard workflow.
 
In the code we use actual_approval_index 3 times for each level of approval,
financial, asset and non-financial. This is working fine however for non
financial approval we call a custom built function to get approvers
maintained in a custom rule with responsibilities, which we set up through
PFAC. The rule has several responsibilities and they on resolving those we
get a list of agents that may come from different responsibilities in the
rule. 
 
When the workitem is sent to these agents, the first person that executes
that approval causes that actual_approval_index (third one, being non
financial approvers) to be complete and therefore standard SAP increments
the approval_index and our badi code checks if the index is greater than 3,
set no_further_approval_required to true.
 
Our problem is that we need each responsibility within the rule to go to the
agents linked to the responsibilities separately and for wait for one of
them to approve/reject before going to the next set of agents from the other
responsibility that matches the criteria. Can we do this? i.e. all agents
must approve for that responsibility before the item is approved?
 
I thought the APPROVAL_BRANCH in the BADI parameters: APPROVAL_TABLE may do
this but I think that might be for sending each step of approvals found for
each actual_approval_index to all agents in parallel can anyone verify this?
 
 
We are on SRM 4.00. Support Package SAPKIBKS08 for SRM_SERVER
 
Thanks in advance
Wayne Rix
wayneri at absa.co.za


___________________________________________________________

Important Notice:
Authorised Financial Services Provider

Important restrictions, qualifications and disclaimers 
("the Disclaimer") apply to this email. To read this click on the 
following address or copy into your Internet browser: 

http://www.absa.co.za/disclaimer

The Disclaimer forms part of the content of this email in terms of 
section 11 of the Electronic Communications and Transactions 
Act, 25 of 2002. 

If you are unable to access the Disclaimer, send a blank e-mail 
to disclaimer at absa.co.za and we will send you a copy of the 
Disclaimer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060714/f8f276c5/attachment.htm


More information about the SAP-WUG mailing list