SRM approval BADI - n Step approval

[Adao-Cruz, Miguel]

Hi,
 
It is not clear if you want:
1) for the last approval step (non finance): at least one user in every
group of approvers (linked with every reponsiblity) to approve in PARALLEL.
It means that if 3 responsibilities, each with user A and B = 6 users
receiving the approval in 3 parallel branches. The shopping cart has to be
approved by 3 users (one for each group).
or
2) for the last approval step (non finance): at least one user in every
group of approvers (linked with every responsibility) to approve in
SEQUENCE. It means that if 3 responsibilities, each with user A and B =
users A1 and B1 receiving the first approval, once one of them approves it
goes to A2 and B2, and so on,,,,
 
Case one can be done with branches (maybe you will have to apply some OSS
note coming in SP09 or 10, look for key words "WSyourWfNumber",
approval_index, n_step, branch.
For case two you have to do it with more than 3 index. If you number of
reponsilities not static then you will have to code
no_further_approval_required = X dynamically.
 
At least that's what I would do...
 
Cheers
 
___________________________________________________________________________
Miguel Adao-Cruz | Capgemini | London
Technology Services
SAP Application Architect

T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com
<file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft
\Signatures\www.capgemini.com> 

Join the Collaborative Business Experience
___________________________________________________________________________

________________________________

From: sap-wug-bounces at mit.edu on behalf of Wayne Rix
Sent: Fri 14/07/2006 14:30
To: sap-wug at mit.edu
Subject: SRM approval BADI - n Step approval


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 --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 8480 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060714/d68032b1/attachment.bin
-------------- next part --------------
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.