Oracle Approver Roles Departure Process


Purpose

This document is meant for Human Resource Partners (HRP) and Supervisors of employees who have approval roles to provide guidance on what to do when an employee leaves the University or vacates their approver role. The steps outlined in this process ensure that the workflow of approvals remains intact when Oracle Approvers leave their role.   

Keep in Mind

Important Role Responsibilities

Please keep the following mind if you have any of these roles:

Approver Role Departure Process

When an employee leaves the University, the Termination Business Process is initiated in Workday by the HRP.  Similarly, if an employee moves positions that results in a vacated approver role, the Job Change Business Process is initiated in Workday by the HRP.

While the HRP initiates the Termination or Job Change Business Processes, the following actions are also necessary if the departing employee has an Approver role.

  1. For all departures, supervisor notifies Human Resource Partner (HRP), who works with Supervisor to quickly re-assign a new PM, OFM, or EFM.
    1. Project Managers (PM)
      1. In the case of a sponsored award (grant):
        1. HRP works with Set-up Specialist to designate an interim PM if a permanent replacement has not been identified.
        2. Supervisor emails aura-help@uchicago.edu to name the interim PM for each applicable project (please provide a spreadsheet of Project that departing approver was overseeing). Email goes to URA so the updates can be made to project personnel in Oracle.
      2. In the case of an IADF:
        1. HRP works with IADF Administrator or Award Admin to designate an interim PM if a permanent replacement has not been identified.
      3. In the case of Capital Project:
        1. HRP works with Capital Project PM to designate an interim PM if a permanent replacement has not been identified
    2. Organization Financial Managers (OFM) and Entity Financial Managers (EFM)
      1. Role Assignment Owner submits an Oracle/Orbit Access Request form to remove the departing OFM or EFM from all applicable organizations and/or entities.
      2. Role Assignment Owner submits a second Oracle/Orbit Access Request form to add a new permanent/interim OFM or EFM to all applicable organizations and/or entities.
  2. New or Interim PM, OFM, or EFM must identify any In-Flight approvals that are not assigned to them.  To help with that, the new PM, OFM, or EFM should run the Invoice Workflow report in the Payables Management Dashboard in Orbit.
    1. For Oracle approvals: New or Interim PM, OFM, or EFM submits an Oracle Approver Reassignment Request for any transactions currently assigned to the previous PM, OFM, or EFM.
    2. For Workday approvals: In-Flight approvals assigned to the resigning PM need to be manually reassigned to the new PM by the Workday Solutions team. Submit an Ask a Human Resources Question request to initiate this process. If a transaction requires PM approval, but there isn't a PM assigned, it will route to the Workday Solutions team where they must determine who the PM is, put the PM into the applicable Workday role, and then reassign the stray transactions.
      1. OFM and EFM approvals do not occur in Workday therefore no action is needed in this system for these roles.
    3. For ServiceNow approvals: In-Flight approvals assigned to the resigning PM need to be updated through a manual script ran by the F&A ITS Service Automation team to reassign to the new PM.  Submit an Ask an IT Question request to initiate this process.
      1. OFM and EFM approvals do not occur in ServiceNow therefore no action is needed in this system for these roles.