The integrity and security of data within the Oracle Financials system is essential, requiring regular review of system access, prompt user access changes and a mindfulness of the Segregation of Duties policy.
The process and associated financial controls have been written in support of the Financial Regulations.
The process of managing users on R12 is as follows:
- The Oxford Username (also known as Single Sign On) is needed for access to Oracle R12 and to monitor related workflow emails.
- If a new user has several Oracle R12 roles, access is granted to each role on the system separately as soon as the user completes the necessary training for each one, instead of waiting for access to all assigned roles once training for all those roles is completed.
- It is important to remove users’ access to R12 when they leave or no longer use the system, since not doing so can cause workflow issues, e.g. leaving multiple projects without a person to approve expenditure and holding up related orders.
- When reviewing the UO User Access Report, authorised signatories may want to be particularly aware of key users who have a major impact on workflow, such as: GL Supervisor (approves other users’ journals); Project Requisition Approver (approves other users’ requisitions when coded to projects); and radiation protection supervisors (a role that exists in some departments for monitoring purposes, where a nominated person is notified when hazardous items are purchased).
- Team names and web links have been updated to reflect the current structure.
indicates steps that require departmental involvement.
indicates work that the Financial Systems Support Centre manages.