EEX 9.2: Expenses Fluid Approvals Enables Users To Insert AdHoc Approvers To Submitted Expense Report Transactions By Starting A New Path, Which Breaks Approvals Sequence (Doc ID 2215903.1)

Last updated on DECEMBER 19, 2016

Applies to:

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

Symptoms

ISSUE:

On approving a submitted Expense Report transaction via the new Fluid Approvals functionality delivered in PeopleSoft Enterprise FSCM 9.2 Image #20, the Users are able to review all the approval paths calculated by workflow by clicking on the Approval Chain button available in the page. At that level, the Start New Path button is available for usage, enabling the Users to define a new User ID as a Reviewer or Adhoc Approver, functionality that does not exist in the Classic Online Approvals (PIA).

REPLICATION STEPS:

     1.- Have an environment patched up to PeopleSoft Enterprise FSCM 9.2 Image #20 level
     2.- Log into the FSCM Online Application as User ID VP1
     3.- Define Expense Report approvals to require at least HR Supervisor approval level
     4.- Log into the FSCM Online Application as User ID EXA1
     5.- Create a brand new Expense Report transaction on behalf of Employee ID KU0021, and submit it for approval
     6.- Log into the FSCM Online Application as User ID EXS1
     7.- Go to Fluid Approvals homepage, and open the submitted Expense Report
     8.- Click on the Approval Chain available button
     9.- Confirm that the system is displaying the different approval level paths calculated (just like in Monitor Approvals page when using Online Classic Approvals)
     10.- Click on the Start New Path button available
     11.- Define a User ID from the valid list of values in the look-up feature
     12.- Click on the Insert Adhoc button
     13.- A new Adhoc approval path gets added online

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ACTUAL RESULTS:

The Approval Chain is available for modification, which means the User is able to Start New Path, and/or add Adhoc Approver, which is not a supported functionality in Expenses (PIA). This can corrupt, or even break the approval sequence, and delay the Employee's reimbursement of the submitted expense.

EXPECTED BEHAVIOR:

The Approval Chain should be read-only for Expense Report, as in PIA also there is no such functionality and this is AWE functionality not supported in Expenses.

 

Cause

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