EEX 9.2: Delegation Request Acceptance and Revoke Functionality Not Correctly Populating nor Clearing Approval Queue of Delegate if Multiple Users Involved (Doc ID 2930509.1)

Last updated on FEBRUARY 27, 2023

Applies to:

Symptoms

Some problems have been detected when an Approver Delegator has submitted a Delegation Request to multiple Delegate Users at the time of Accepting and Revoking the requests.

  1) The first Delegate accepting a submitted Delegation Request will automatically get re-routed all pending Expense Reports from the Delegator's queue. However, any sub-sequent Delegate User accepting the same Delegation Request will not get the same transactions re-routed into their queue.

  2) If the Delegation Request is revoked by the Delegator, all those Expense Report transactions submitted for approval after the Delegation Request got accepted will be re-routed back to the main Delegator, except for those of secondary Delegate Users that accepted the Delegation Request on second or later steps

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator User
    2.- Enable HR Supervisor at the Transaction Definition level
    3.- Set up Employee A as the HR Supervisor of Employee XYZ at the Expenses Profile level
    4.- At the PeopleTools Profile level, set up the EODL_User Role to Users A, B, and C
    5.- Log into the FSCM Online Application as Expenses XYZ Employee
    6.- Proceed to create, and submit, a brand new Expense Report for Employee XYZ
    7.- Confirm that the Expense Report has been routed to HR Supervisor User A
    8.- Log into the FSCM Online Application as Expenses Approver User A
    9.- Go to the Fluid Approval pages, and confirm that the Expense Report transaction is currently listed in the pending queue
    10.- Proceed to create a new Delegation Request for Expense Report transactions, from last week, and for the upcoming 3 more weeks, and define Users B and C
    11.- Submit the Delegation Request just created
    12.- Log into the FSCM Online Application as Expenses Approver User B
    13.- Accept the Delegation Request submitted by User A
    14.- Go to the Fluid Approval pages, and confirm that the Expense Report transaction is currently listed in the pending queue
    15.- Log into the FSCM Online Application as Expenses Approver User C
    16.- Accept the Delegation Request submitted by User A
    17.- PROBLEM #1: Go to the Fluid Approval pages, and confirm that the Expense Report transaction is NOT being listed in the pending queue
    18.- Log into the FSCM Online Application as Expenses Approver User A
    19.- Go to the Fluid Approval pages, and confirm that the Expense Report transaction is no longer being listed in the pending queue
    20.- Log into the FSCM Online Application as Expenses XYZ Employee
    21.- Proceed to create, and submit, a second Expense Report for Employee XYZ
    22.- Confirm that the Expense Report has been routed to HR Supervisor with multiple Users, B and C
    23.- Log into the FSCM Online Application as Expenses Approver User A
    24.- Go to My Delegates, and proceed to revoke the Delegation Request previously created, and accepted by Users B and C
    25.- Go to the Fluid Approval pages, and confirm that the Expense Report transaction is once again being listed in the pending queue
    26.- Log into the FSCM Online Application as Expenses Approver User B
    27.- Go to the Fluid Approval pages, and confirm that the Expense Report transaction is no longer being listed in the pending queue
    28.- Log into the FSCM Online Application as Expenses Approver User C
    29.- PROBLEM #2: Go to the Fluid Approval pages, and confirm that the Expense Report transaction is STILL being listed in the pending queue

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.

Expense Reports being submitted prior to the Delegation Request being accepted are not being automatically re-routed to all the needed User IDs, and once the Delegation Request is being revoked, the transactions are not being re-assigned back to the Delegator for all Delegate Users. This confuses all Users involved with the workflow of Expense Reports, and potentially delays approvals, and subsequent reimbursements.

If Users B and C accept the Delegation Request from Delegator User A, workflow should re-route all submitted Expense Reports to ALL accepting Delegates, not only the first one to accept the request. Equally, once a Delegation Request is revoked by the Delegator, workflow should re-route back the involved Expense Report transactions for ALL Delegate Users, not only some.

Cause

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