My Oracle Support Banner

EAP: Payment Request Is Approved And Not Routed to Admin When Submitted By Reviewer (Doc ID 2709464.1)

Last updated on SEPTEMBER 10, 2020

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Payment Request Template is setup with 'Review before Workflow Approval'.  Payment Request is created by a User who is not assigned a Supervising User ID. Reviewer reviews the Payment Request and submits the Payment Request. In the Error Step, Payment Request is Not Routed to a User with the Admin Role yet the Payment Request is Approved.

The Payment Request should be Pending and routed to an Admin since the User who created the Payment Request was not assigned a Supervising User ID.

STEPS
1. Payment Request Template
   Template Name = TEMPLATE_A
   'Review before Workflow Approval' is selected
   Reviewer Role = Y AP PR REVIEWER 

2. Approval Process Setup
    Process ID = PaymentRequestApproval
    Definition ID = PaymentRequestApprvl
    Admin Role = Y AP WF ADMIN

3.  User ID = AAL3A is not assigned a Supervising User ID (PeopleTools > Security > User Profiles > User Profiles > Workflow)

4.  User ID = AAL3A creates a Payment Request and Submits for Approval

5.  User ID = AASXB (Has Y AP PR REVIEWER Role), Reviews and Submits the Payment Request

6.  Approval Flow for the Payment Request has the following:

REQUEST_ID=0000010519:Approved

Route to Supervisor

Not Routed
Multiple Approvers
Error Step
  
Comments
   System at 07/29/20 - 4:14 PM
  Not enough approvers were found at: step number 0, path 1, stage 10. Routing to Admin.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.