How do the SRM-EBP Approval and Spend Limits work

[Dart, Jocelyn]

Hi Jerry,
The ROLE attribute is only for the workflow scenario where users can apply for a userid
and that is sent to their manager for approval - in which case the ROLE attribute is used
to control which roles the manager can assign to new users.
Other than that its not used so far as I know.
 
So attach your security roles to your users as normal.
 
If you a looking for a subsitution approach the EBP inbox lets you set up HRUS_D2
user-to-user workflow substitutions.
 
As always, if you make someone your substitute then its up to you to ensure they have
the relevant piece of paper with signature or whatever required for the audit guys.
 
I wouldn't attempt to limit who you can substitute to - the workflow log records who
actually did what very well these days and in any case even requestors need substitutes
from time to time.
Jocelyn
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Martinek, Jerry
Sent: Wednesday,14 April 2004 1:41 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How do the SRM-EBP Approval and Spend Limits work
 
 
Hi Jocelyn,
 
If we use a security role, should it be attached to the position or the user
or does it depend? What is the purpose of the ROLE attribute at the position
object?
 
If you attach the authorization role to the position, will the people ( Full
time and Acting assignments) assigned to that position able to approve as
specified in the role or do you need to do something else?
 
Thanks,
Jerry Martinek
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Monday, April 12, 2004 11:39 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How do the SRM-EBP Approval and Spend Limits work
 
 
Jerry,
It's the usual ... more options than you can poke a stick at.
 
Basically its an either/or choice depending on what best suits your
organisation. That is:
 
Either: Use the organisational hierarchy to set spending/approval limits
(which lets you set it at organisational unit level, inherit to or override
at lower org units/positions) if your spending/approval limits are aligned
to your reporting structure.
 
Or: Use security roles to set spending/approval limits (with the option of
overriding the values in the user master) if your spending/approval limits
are aligned to user authorizations.
 
It doesn't usually make business sense to use both approaches in the one
system.
 
It is explained in the SAP library help doco for SRM - have a look at the
help.sap.com site under Cross Industry Solutions if you can't find a copy
locally.
 
Spending limit - what you can spend in your own shopping carts without
requiring approval Approval limit - up to what limit you can approve when
other shopping carts are sent to you for approval (used to decide if we need
other people involved in the approval scenario or not).
 
Hope that helps.
Jocelyn
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Martinek, Jerry
Sent: Friday,9 April 2004 4:51 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: How do the SRM-EBP Approval and Spend Limits work
 
 
Hi,
 
I'm trying to get an understanding on how the approvers spending/approval
limits processing works withing the EBP 4.0 approval process.
 
I know that you can specify the approval limit amount at the Organizational;
Position and User levels. If that is the case, what would you specify in an
approver  'ROLE' that is assigned to a Position held by an approver? How
does this work?
 
How does this resolve in the EBP system? Can someone provide an explanation
on how this works; link to some understandable documentation or the code
that implements this functionality?
 
Also, when you set the Organization or Position 'Approved for value limit'
Attribute as well as the 'Approval Limit' in the Extended Attributes PO
Value limits, what does this mean?
 
 
Regards,
Jerry Martinek