EEX 9.2: The Approval Workflow Engine Tool (AWE) In Expenses Is Not Properly Routing A Submitted Expense Report To The Expected Approver User On HR Supervisor Level If Designated Approver Is Populated At Expenses Profile Instead Of Supervisor ID
(Doc ID 2245419.1)
Last updated on FEBRUARY 03, 2019
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Expenses Approval Workflow feature is not routing properly submitted Expense Reports to the HR Supervisor level if at the Expenses Profile, for the Employee owner of the transaction, the Supervisor ID field is blanked out, and the Designated Approver field is populated instead, (Record Field PS_EX_EE_ORG_DTL.APPROVER_OPRID).
Workflow does not seem to find the proper User ID, and routes the transaction to the Expense Report Transaction Definition User defined at field Approval System Administrator.
1.- Activate HR Supervisor approval level for Expense Report Transaction Definition
2.- At the Expenses Profile level, for Employee ID KU0008, blank out Supervisor ID field, and define User ID MGR3 into Designated Approver field
3.- Submit an Expense Report transaction on behalf of Employee ID KU0008
4.- Check how Expenses Workflow has routed HR Supervisor level to the Approval System Administrator User ID GLS4 defined at Transaction Definition level, and not the expected User ID MGR3
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.
Workflow Approval is not routing the submitted Expense Reports to the expected Approver Users, which delays the review, and approval of expenses to be reimbursed.
The Approval Workflow Engine tool (AWE) should be able to identify whether a Supervisor ID or a Designated Approved has been defined at the Expenses Profile level, and according to that, route the submitted Expense Report to the proper Approver user for further action.
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