EEX 9.2: Fluid Approvals Push Back Button Not Clearing Expense Report Line Risk Details From Record PS_EX_RISK_ER_DTL
Last updated on OCTOBER 24, 2017
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
It has been detected a system inconsistency between Classic Online Approvals, and Fluid Approvals. Whenever Risk Template configuration is used on Location Amount validations, workflow appropriately flags those Expense Report Lines that exceed the defined Authorized Amounts per Location. If the Expenses Approver sends back for revision the Expense Report routed, through the Online Classic Approvals functionality, the system automatically deletes the transaction's entry into Record PS_EX_RISK_ER_DTL.
However, if instead of Online Classic, the Expenses Approver does the same action within Fluid Approvals interface, and hence, instead of using the Send Back For Revision button, its equivalent Push Back button is used, the transaction's data in Table PS_EX_RISK_ER_DTL is not being cleaned up.
As a result, even if the Employee subsequently lowers the Transaction Amount of the offending Expense Line, and resubmits for approval the transaction, the Risk Details comments remain, and the line is kept as flagged throughout approvals.
1.- Enable Expenses Approval Workflow for Expense Report transactions so that HR Supervisor level is required
2.- Define a new Risk Template where the setting Authorized Amount Exceeded = Y
3.- At the Approver Profile for HR Supervisor, link the Risk Template, and save the changes
4.- Define an Expense Location Amount of 100 USD for Expense Type DINNER, and Location ABC
5.- As an Expenses User, create a new Expense Report with one line using Expense Type DINNER, Location ABC, and a Transaction Amount of 150 USD
6.- Submit the newly created Expense Report for approval
7.- Log into the FSCM Online Application as the HR Supervisor approver
8.- Go to the Fluid Approvals Homepage, open the routed Expense Report, and select Push Back button, stating in the comments that the expensed amount is too high to be approved
9.- As the Employee, proceed to update the returned Expense Report, lowering the expensed line amount to 90 USD, lower than the maximum allowed, and re-submit for approval
10.- As HR Supervisor approver, note that the Risk Details comments have not been cleared up, and the Expense Report is still flagged as risk with the below message:
" Authorized Amount Exceeded. "
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.
The resubmitted Expense Report transactions have the affected line still flagged with Risk Details, even if the Transaction Amount has been addressed with a lower amount than the authorized for the location chosen. This confuses the Expense Approvers, and leaves incorrect audit records.
Fluid Approvals functionality should be consistent, and follow the steps of the Classic Online feature, where the Expense Report line row in Record PS_EX_RISK_ER_DTL gets deleted upon Push Back button is selected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms