My Oracle Support Banner

ECM: Treasury Settlements Approval Not Following Dynamic Path / Supervisor By Userid When Selecting Settlement Payment (Doc ID 2791225.1)

Last updated on JULY 14, 2021

Applies to:

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

Goal

Treasury Options is setup with Settlement Approval Method = Approval Framework.

Approval Process ID = TreasurySettlementsApproval is setup with a Dynamic Path and a Step with Approver User List = Supervisor by UserId.

After EFT Request is created, the Originator (User 1) of the EFT Request selects the Settlement Payment. Approval Workflow is routed to the Approver (User 2), who is the Supervisor of User 1. User 2 un-selects the Settlement Payment, makes a change to the EFT Request, and selects the Settlement Payment. Approval Workflow is still routed to User 2, and User 2 is able to approve the Settlement Payment.

Customer believes that since the Approver User List = Supervisor by UserId, once User 2 makes a change to the EFT Request and selects the Settlement, the Approval Workflow should be routed to the Supervisor of User 2. User 2 should not be the one that is able to approve the Settlement since User 2 made a change to the EFT Request. To the Customer, this is an audit issue.

Is the system Working As Designed or is this considered a Bug?

Solution

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
Goal
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.