<!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.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>Hello
all,</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>This is my first
post here so please be patient if my question is completely
silly.</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>We have implemented
the standard n-step approval badi here for determining our shopping cart and
purchase order approvers using the standard workflow.</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>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. </FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>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?</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>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?</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>We are on SRM 4.00.
Support Package SAPKIBKS08 for SRM_SERVER</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>Thanks in
advance</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2>Wayne
Rix</FONT></SPAN></DIV>
<DIV><SPAN class=328392012-14072006><FONT face=Arial size=2><A
href="mailto:wayneri@absa.co.za">wayneri@absa.co.za</A></FONT></SPAN></DIV><P>
<BR>
___________________________________________________________<BR>
<BR>
Important Notice:<BR>
Authorised Financial Services Provider<BR>
<BR>
Important restrictions, qualifications and disclaimers <BR>
("the Disclaimer") apply to this email. To read this click on the <BR>
following address or copy into your Internet browser: <BR>
<BR>
http://www.absa.co.za/disclaimer<BR>
<BR>
The Disclaimer forms part of the content of this email in terms of <BR>
section 11 of the Electronic Communications and Transactions <BR>
Act, 25 of 2002. <BR>
<BR>
If you are unable to access the Disclaimer, send a blank e-mail <BR>
to disclaimer@absa.co.za and we will send you a copy of the <BR>
Disclaimer.<BR>
</BODY></HTML>