cancel
Showing results for 
Search instead for 
Did you mean: 

Substition - n-Level Output Limit Approval Process

Former Member
0 Kudos

Hi,

we are using a process-controlled workflow in SRM 7.0; n-Level Output Limit Approval Process; see BC-Sample process scheme 9C_BUS2121_EX03.

Situation 1: a manager (approval limit 3.000) sets an user (without approval limit entry in the OrgMgmt) as substitute. The substitute succeeds in approving a purchase order.

The purchase order is approved despite the missing approval limit of the substitute. Even exception entry "Calling class /SAPSRM/CL_WF_RULE_CONTXT_SC method PREV_APPROVAL_LIMIT

raises error exception

Message no. /SAPSRM/BRF086"

in SLG1 does not disturb the approval. The exception-entry itself is fine; however the approval is not supposed to succeed if such an exception happens.

Situation 2: a manager (approval limit 3.000) sets an user (approval limit 1.000) as substitute. The substitute can now approve up to 3.000 without additional approver. This is not the expected result.

Do you know any solutions for these problems?

Best regards,

Frank

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello,

we are going to solve this problem with BAdI WF_SUBSTITUTE.

Best regards,

Frank

Edited by: Frank Scheler on Feb 8, 2011 1:22 PM

Former Member
0 Kudos

Hi,

if the workflow isn´t errored out in this case: is there any way to error out the workflow in a customer method (replacing /SAPSRM/CL_WF_RULE_CONTXT_SC method PREV_APPROVAL_LIMIT)?

Regards

Former Member
0 Kudos

Hi,

What is your business requirement? if you want to stop not ordering the SC if the substitute approval limit is less than the system determine approver approval limit.. try to implement the logic in BBP_DOC_CHECK_BADI.. where you have to build the same logic to find the substitute approval limit.. if the approval limit is less , then error out..

Saravanan

Former Member
0 Kudos

Hi,

the bussiness case is that no approver must be allowed to exceed his/her approval limit. This includes substitution.

Regards,

Frank

Former Member
0 Kudos

Hi,

Meaning.. requester should not be able to create a SC if the approval limit exceed the approval limit right? if then.. imiplement the logic in BB_DOC_CHECK_BADI... check all the approver's approval limit.. if any one of the approval limit exceeds then raise a error message..

Saravanan

former_member206968
Active Contributor
0 Kudos

Hi,

You will have to modify the substitution program such that,no users should be able to select a substitute having lower approval limit. This would achieve the desired functionality.

Regards,

Sanjeev

Former Member
0 Kudos

Hi Saravanan,

is it OK that that the approval succeeds in situation 1 (despite the error-message in SLG1)? Shouldn´t the WF go to status error?

Regards,

Frank

Former Member
0 Kudos

Hi,

I dont think this kind of error message force the workflow to be errored out, because checking the approval limit happens at the time of ordering the SC.. and class '/SAPSRM/CL_WF_PDO_SC~HANDLE_PROCESS_FINISHED' would not do the all the checks .

Saravanan.

Former Member
0 Kudos

Hi,

Approval limit and Spending limit are using to determine the approver's for a SC/PO. once system find the correct approver's based on the expression, system won't check the approval limit of a substitute that assign for a determined approver.

Saravanan