cancel
Showing results for 
Search instead for 
Did you mean: 

Spending Limit Approver, SLAPPROVER attribute

Former Member
0 Kudos

Hi,

We have a requirement to implement the SLAPPROVER concept. I have few doubts regarding this.Could any please share some info.

1. Multiple SLAPPROVER attribute

In the user attribute, we will add the managers name in the SLAPPROVER(so that the system picks the manager as aapprover, if spending limit is less than SC value). In this process,  for a particular user, can we have two SLAPPROVER attributes? If so how will the system pick the approval flow?

for ex :  can we have like this ?

for User A;

SLAPPROVER : 'X'

SLAPPROVER : 'Y'.

2. Badi Impelmentation

For the badi /SAPSRM/BD_WF_RESP_RESOLVER, we have an implementation  /SAPSRM/BD_WF_SC_RR_SL which is used to find the spending limit approver.

During the call of the above mentioned implementation will the badi/SAPSRM/BD_WF_PROCESS_CONFIG is called?(as this were the process levels will be created dynamically).

3. Sequence of workitem generation

Using the SLAPPROVER concept, will the generation of workitems will be in sequential order?

Like, user 'A' created SC with value of 5000 EUR and his SLAPPROVER's person 'X' approval limit is 3000 EURs.

as the SLAPPROVER approval limit is less than SC value, it will find the SLAPPROVER of person 'A', in this case the SLAPPROVER for A is person 'B'(whose approval limit is 6000 EUR).

will the work items get genearted for both persons A and B (or) the workitems will be generated for only person 'B'.

Could any clarify, thank you in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

The attribute SLAPPROVER determines the organizations for which you are responsible if the workflow for spending limit triggers.

Suppose the employee (under organization O 50000230) has a spending limit of 500 $ and he orders a shopping cart for 600 $ then the workflow for spending limit triggers (If BRF workflow is used then there are events and responsible resolver available for spending limit workflow) . System looks for the user who is responsible for the organization O 50000230 and finds him/her as the approver of the shopping cart.

So User A can be responsible for multiple organizations

SLAPPROVER : O 50000230

SLAPPROVER : O 50000300

There will always be one work item only for each approval level. There will be multiple agents assigned for the approver position.

With Regards,

Malay

Former Member
0 Kudos

Hi,

I have figured out how it works, SLAPPROVER will work based on the user level attributes.

For ex : If Person 'A'  is creating shopping cart, and if his SLAPPROVER is maintained as 'B' - then system will check the spending limit of person A, and if SC total value is more than  user spending limit, then SC will go for person 'B' approval.

If SC value is more than the person 'B' approval limit, then approval will go for SLAPPROVER of Person 'B'.(for ex : C)

work items will be generated sequentially like B,C etc... or workitem can go directly for the last person to approve(i did not work on this case).

the below link can also be checked for reference.

http://help.sap.com/saphelp_srm701/helpdata/en/a7/465d4716bc443687ae29679934f25b/content.htm

First system will call /SAPSRM/BD_WF_PROCESS_CONFIG to create the process levels, in this badi only system will pick the SLAPPROVER based on spending limit.

then the badi /SAPSRM/BD_WF_RESP_RESOLVER , Responsible resolver name as /SAPSRM/BD_WF_SC_RR_SL is called during the creation of decision sets.

Former Member
0 Kudos

Hi,,

One thing i would like to add here is..

Yes If SC value is more than the person 'B' approval limit, then approval will go for SLAPPROVER of Person 'B'.(for ex : C ).

But in case if approval limit of person B and person C is maintained same value. Then any shoping cart A raises, which is of more than his spending limit  would go to person C (person at higher level of workflow) for approval.

Regards,

Asad