How to implement Reject and Send for Revision action for Dynamic Agent Parallel Approval for BRFplus

[Baunach, Natasha R]

Hi Rick,

Here is a screenshot.
[cid:image001.png at 01D56ED0.7B097D10]

Susan also opened OSS message and I am attaching those details as well.

Thanks again for your help.  If after reviewing this, you still feel that terminating event is the way to go, I will advise that team accordingly.
Natasha

From: sap-wug-bounces at mit.edu <sap-wug-bounces at mit.edu> On Behalf Of Rick Sample
Sent: Thursday, September 19, 2019 9:01 AM
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Cc: Wang, Susan <susan.wang at intel.com>
Subject: Re: How to implement Reject and Send for Revision action for Dynamic Agent Parallel Approval for BRFplus

Simple. Email graphic screen print, and I'll walk you through it. Been doing this 15 yrs and know exactly how you want this to flow.

Rick

Rick Sample | Workflow Analyst/Developer
Corporate - Centerpoint, MO | Office (314) 573-5822 | rick.sample at graybar.com<mailto:rick.sample at graybar.com>
www.graybar.com<http://www.graybar.com> - Graybar Works to Your Advantage

________________________________
From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> <sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu>> on behalf of Baunach, Natasha R <natasha.r.baunach at intel.com<mailto:natasha.r.baunach at intel.com>>
Sent: Thursday, September 19, 2019 10:48:47 AM
To: sap-wug at mit.edu<mailto:sap-wug at mit.edu> <sap-wug at mit.edu<mailto:sap-wug at mit.edu>>
Cc: Wang, Susan <susan.wang at intel.com<mailto:susan.wang at intel.com>>
Subject: How to implement Reject and Send for Revision action for Dynamic Agent Parallel Approval for BRFplus


Hi,



We are using standard Ruled-Based Workflow for Customer Maintenance.  We are using is a copy of CUST1P2 for Create Customer, and use "WS60800086" ruled-based workflow.  We are also using Dynamic Agent Selection and Parallel Merge capabilities, so that system can determine appropriate approver(s) based on business rules, and enable multiple approvers to approve (parallel approval, not sequential approval) before a Create Customer change request is activated and customer is created.  We allow approver to Approve, Reject, or Send for Revision.



System is working fine if all approvers approve, as CR status will be set to "Final Check Accepted" and customer will be created.



System is not working for Reject. Right now when one approver rejects, and there are other approvers which have not taken action, system waits for other approvers to take action before it sets the CR status to "Final Check Rejected". Desired result is for system to immediately set the CR status to "Final Check Rejected" when the approver rejects, and remove the approval task from other approver's queue or set other approval tasks that are in "Ready" status to "Completed", so system shows the CR is rejected, and all tasks are complete.



System is also not working for Send for Revision.  Right now when one sends CR for revision, and there are other approvers which have not taken action, system waits for other approvers to take action first, and depending on Approve or Reject from approvers, CR is either "Final Check Approved" or "Final Check Rejected". Desired result is to have the system complete tasks from other approvals queue, send the CR back to requester for revision, and if requester resubmits, system should redetermine approvers.



Likely will be some development involved, can anyone advise what type of development is involved to achieve the desired results for Reject action and for Send for Revision action?  Appreciate any inputs.


Thank you!
Natasha Baunach
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20190919/d7c50b50/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 157155 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20190919/d7c50b50/attachment-0001.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SAP Incident 523563 Reject Action on Parallel Approval does	not work for....docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 688187 bytes
Desc: SAP Incident 523563 Reject Action on Parallel Approval
	does not work for....docx
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20190919/d7c50b50/attachment-0001.bin