EAP: Unpredictable Routing When Approver Not Found In Previous Step in Payment Request Approval (Doc ID 2128765.1)

Last updated on APRIL 19, 2016

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Goal

When no approvers are found in an approval step, the approval request is getting routed to approvers from other steps, even though the criteria for these steps should not allow any routing to those users/approvers.

Expectation is the step after the no approver error step to perform the criteria check on each subsequent step until it gets to another step matching the business unit criteria. If it gets to the end of the steps without an approver, then we'd like it to go to the admin.

For example in following is using Business Unit criteria for Payment Request:

Approval Process Step # 1 for BU = US001

Approval Process Step # 2 for BU = US002

Approval Process Step # 3 for BU = US003

Approval Process Step # 4 for BU = US001

 

Create Payment Request for US001.

When there are no approvers in Step # 1, getting following result:

Approval flow shows Step # 1 ( BU US001) was skipped because No approvers found for Approval User List US001 (correct)

Workflow is routed to next Step # 2 which is for BU = US002 with status Pending (incorrect) and Step # 4 shows up for US001 with status 'Not Routed'(correct)

Step # 1 for US001 (Skipped) -> Step # 2 for US002 (Pending) -> Step # 4 for US001 (Not Routed)

Note: Approval Request is not routed to Step # 3 which is correct.

Expected result is Step # 1 for US001 should show 'Skipped' and the Approval request to get routed to Step # 4 directly instead of going to step # 2 which is for BU = US002 .

Step # 1 for US001 (Skipped) -> Step # 4 for US001 (Pending)


 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms