EECO 9.2: Fluid Delegation Request Not Sending Any Email Notifications to Interested Parties When Using Administer Create Delegation on Behalf of Another User (Doc ID 2854427.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

When a Functional User submits a Delegation Request from the Administer Create Delegation Page/Component on behalf of another User, to temporarily re-route the Expense Report approvals to a Delegate/Proxy User, the system does generate a new Delegation Request that goes to the Proxy's Manage Delegation queue, to review, and accept/reject. If accepted, whenever an Expense Report is created, and submitted for approval, the workflow recognizes the new delegated Proxy User, and routes the transaction to both the original Approver, and the Delegate/Proxy User.

However, the delivered Approval Process ID FluidDelegation is not generating the corresponding Email Notifications to inform the Proxy that a Delegate Request has been submitted for them to accept.

This only takes place when using Administer Create Request, and on behalf of a third User, not oneself.

REPLICATION STEPS:

   1.- Log into the FSCM Online Application as an Expenses User ID EXS1
   2.- Navigate to: Enterprise Components > Delegation > Administer Create Delegation
   3.- Define User ID EXS2
   4.- Click on Create Delegation button
   5.- On Step 1 (Delegation Dates), define a Start Date, End Date, Comments, and click on NEXT button
   6.- On Step 2 (Delegates), click on ADD DELEGATE button, choose User ID EXS3, select it, and click on NEXT button
   7.- On Step 3 (Transactions), select the Expense Report flag, and click on NEXT button
   8.- On Step 4 (Review and Submit), review the information entered, and click on the SUBMIT button
   9.- ISSUE: Confirm that on the Email Account of User ID EXS3, there is no Email Notification of this new Delegation Request

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

As no Email Notifications are being received by all Delegation Request Users involved, there is no indication that the Users should go to the Manage Delegation page to review if any Request has been submitted, and as such, some may be missed, and not be acted upon in time. This may cause transactions be routed to the incorrect Users for approval, and further delay approvals.

As in PeopleBooks is mentioned, Email Notifications should be sent out to all involved Employees (Delegators, and Proxies), so they can act quickly, and promptly on any submitted Delegation Requests.

Changes

Cause

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