cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Reject button Issue - GRC 10

Former Member
0 Likes
1,079

Hi All,

I have a query regarding REJECT in OTHER ACTIONS button in GRC.

In my workflow I have maintained task settings as below.

Approval Level - Role

Rejection Level - Role

Individual Line Items I am able to Approve/Reject using the Approve or Reject buttons.

I tested below scenario.

Created a GRC request with 2 roles. Both roles have different role owners.

Request once completed in first stage went to 2 role owners separately with their respective roles.

First role owner opened the request, went to other actions -> Reject and rejected the entire request.

Because of this entire request got rejected and closed irrespective of other role owners action.

I wanted to disable REJECT option under Other Actions in role owner stage.

I have already went through various discussions in the forum but couldn't find any

https://scn.sap.com/thread/3211542

http://scn.sap.com/thread/3367477

http://scn.sap.com/thread/3272504

http://scn.sap.com/thread/3485469

http://scn.sap.com/thread/3504767

http://scn.sap.com/thread/3151204

Please help if anyone faced the same issue

Regards,

Sai

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Likes

On SP12 and 13, only workaround I know of is to actually ensure the individual line items are "Approved/"Rejected" properlly and then press "Submit"......not great, but it seems that the coding logic of how the "Approve/Reject" works by pressing "Reject" as a button is confusing.

alessandr0
Active Contributor
0 Likes

Dear Sai,

the task settings as mentioned above is for role owner stage? Whats your SP level?

See also the following document:

http://service.sap.com/sap/support/notes/2009668

Regards,

Alessandro

Former Member
0 Likes

Hi Alessandro,

We are on SP13.

Screenshot provided is of task settings of role owner stage.

Regards,

Sai.

alessandr0
Active Contributor
0 Likes

Hi Sai,

okay - I have shortly checked and reviewed some notes.

The button Other Action > Reject is for rejecting the ENTIRE request irrespective of what the status is at "Approval Status" field in line-item level. Once you press the reject button, the Rejection Email notification would be sent with the line-item level status as maintained in "Approval Status" field. This means you have rejected the request, and the roles OR line-items approval status would not be considered.

Means you have to restrict via authorization or via the GUI so that this button is not avaiable. With standard MSMP settings it couldn't be set as you want.

Regards,

Alessandro

Former Member
0 Likes

Hi Alessandro,

Thanks for the details. I have checked all the available authorization objects but couldn't find any. This issue would be there for all the users who are using GRC 10.

Hopefully someone might have had a workaround for this issue. Will check.

Regards,

Sai.

FilipGRC
Contributor
0 Likes

Hi Sai,

I believe this is a SP13 functionality problem issue - maybe upgrade to SP15 will solve the issue.

According to SAP Documentation - what you have described should not be the case as under the Task Settings section, SAP advise to select the checkboxes for the features you want to be available to approvers on the access request screen. Rejection level allows approvers to approve requests for the following levels:

  • Request

Approvers have the authority to approve all roles in a request. For example, security approvers can approve any role relevant to a request. Role Approvers can approve only those roles that belong to them.

  • System and Role

Approvers have the authority to approve systems and roles.

So taking into account what is described - it should work as you requested, so maybe this is SP13 issue, migrate to SP15 and let us know,

Filip

Former Member
0 Likes

Hi Filip,

Yes you are right. Though I maintain task level settings for Approval Level and Rejection Level as "ROLE", Role owners are able to reject the entire request. I am raising this issue to SAP and will check if there is any SAP note or workaround for this issue in SP13

Regards,

Sai.