EBP 4.0 - SC N-Step Approvals and Approval Limit Values

[Dart, Jocelyn]

Hi Jerry,
In EBP 4.0 i.e. SRM 3.0, the change approver can be any possible agent of the approval task.
There's no other check.
In EBP 5.0 i.e. SRM 4.0, there are two new BADIs to apply business rules to control:
* Whether add/change approver can be used
* Who can be chosen as an alternative approver.
 
Approval limit is used to determine the original approver only in EBP 4.0.
 
Jocelyn
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Martinek, Jerry
Sent: Tuesday,1 June 2004 4:33 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP 4.0 - SC N-Step Approvals and Approval Limit Values
 
 
Hi,
 
Can someone please confirm that the 'Approval Limit' value doesn't seem to
play a role in checking/restricting the approval of a shopping cart if its
value exceeds the approvers 'Approval Limit' value.
 
If the task's (TS10008126) list of possible agents includes approvers with
different approval limit values (ie. 100K, 250K, 500K, etc..), the system
doesn't seem to stop you from overriding the system derived approver for a
500K approval step with one that doesn't have that amount and then the
system at time of approval assumes that they must be authorized since they
got the work item.
 
In R3, when you specify various values for the authorization object fields,
the system seems to enforce these at execution time. I guess that the
'Approval Limit' value doesn't work that way.
 
Does anyone have any experience with this?
 
Thanks,
Jerry Martinek