Oracle Audits
Currently, the City of Atlanta uses the Oracle eBusiness Suite to handle financial, procurement, and human resource functions. Before the implementation of Oracle, the city used several computer systems that were organized around separate departments. Our office performed multiple audits on the transition from this previous system to the current deployment of Oracle.
Reports located elsewhere on our website:
Reports located elsewhere on our website:
- Pre-Implementation Review of ERP - November 2005
- Oracle ERP Implementation Audit Update - March 2007
- Oracle Implementation Contractor Oversight - March 2007
- KPMG ERP Pre-Implementation Assessment - July 2007
- Oracle First Payroll Run - April 2008
Other reports on the Oracle implementation process:
Oracle To-Be Processes - August 2005
This memo includes our preliminary recommendations on design of controls for the city’s Oracle Enterprise Resource Planning (ERP) phase 1 implementation. We have reviewed the proposed to-be processes that the city envisions using when the ERP implementation is completed.
Oracle Target Blueprint - September 2005
This memo includes our preliminary recommendations on the Oracle ERP Target Processes for the city’s Oracle Enterprise Resource Planning (ERP) phase 1 implementation. The focus of this memo is a review of the Oracle ERP Target Process Blueprint document.
HRMS applications round 2 CRPs - April 2006
This memo focuses on controls and processes associated with the Human Resources Management System (HRMS) applications.
HRMS, Financial and Procurement applications round 3 CRPs - July 2006
This memo focuses on controls and processes associated with the Human Resources Management System (HRMS), financial, and procurement applications.
Conference Room Pilot 3.5 for Financial Applications - November 2006
The memo details our review of the Conference Room Pilots. Based on our attendance of the CRPs and interviews with city staff and consultants regarding Oracle functionality, we concluded that the ERP project team identified reasonable solutions to the issues discussed in the CRP.
Review of the Finance, HRMS, and Purchasing Responsibility Matrices - January 2007
In this review we concluded that the Finance, HRMS, and Purchasing applications were properly segregated so that no one employee could perform incompatible functions.
Audit Trail Configuration in Oracle - February 2007
This memo makes recommendations on how the city should configure the audit trail and other security features in Oracle to prevent and detect unauthorized changes to data and settings.
Remaining Audit Work on the Oracle Implementation - February 2007
This memo lists several remaining projects scheduled to review and provide assurance on specific aspects of the implementation.
Follow-up on Oracle Implementation Recommendations - February 2007
This memo shares our plans for following up and verifying that agreed-upon audit recommendations have in fact been included in the Oracle system configuration.
Assignment of Employees to Oracle Responsibilities - March 2007
We reviewed responsibility assignments submitted by the departments of Aviation and Police to ensure that individual employees are not assigned incompatible business functions within the Oracle system. We identified some inconsistencies between the departments’ submissions and current project team designations. We also identified a few employees whose proposed responsibilities could combine incompatible duties.
Review of Incompatible Duties across all Responsibilities within Oracle - April 2008
Our objective in this most recent review was to examine the assignment of users to multiple responsibilities to determine whether the assignments allow users to perform incompatible duties.
Oracle To-Be Processes - August 2005
This memo includes our preliminary recommendations on design of controls for the city’s Oracle Enterprise Resource Planning (ERP) phase 1 implementation. We have reviewed the proposed to-be processes that the city envisions using when the ERP implementation is completed.
Oracle Target Blueprint - September 2005
This memo includes our preliminary recommendations on the Oracle ERP Target Processes for the city’s Oracle Enterprise Resource Planning (ERP) phase 1 implementation. The focus of this memo is a review of the Oracle ERP Target Process Blueprint document.
HRMS applications round 2 CRPs - April 2006
This memo focuses on controls and processes associated with the Human Resources Management System (HRMS) applications.
HRMS, Financial and Procurement applications round 3 CRPs - July 2006
This memo focuses on controls and processes associated with the Human Resources Management System (HRMS), financial, and procurement applications.
Conference Room Pilot 3.5 for Financial Applications - November 2006
The memo details our review of the Conference Room Pilots. Based on our attendance of the CRPs and interviews with city staff and consultants regarding Oracle functionality, we concluded that the ERP project team identified reasonable solutions to the issues discussed in the CRP.
Review of the Finance, HRMS, and Purchasing Responsibility Matrices - January 2007
In this review we concluded that the Finance, HRMS, and Purchasing applications were properly segregated so that no one employee could perform incompatible functions.
Audit Trail Configuration in Oracle - February 2007
This memo makes recommendations on how the city should configure the audit trail and other security features in Oracle to prevent and detect unauthorized changes to data and settings.
Remaining Audit Work on the Oracle Implementation - February 2007
This memo lists several remaining projects scheduled to review and provide assurance on specific aspects of the implementation.
Follow-up on Oracle Implementation Recommendations - February 2007
This memo shares our plans for following up and verifying that agreed-upon audit recommendations have in fact been included in the Oracle system configuration.
Assignment of Employees to Oracle Responsibilities - March 2007
We reviewed responsibility assignments submitted by the departments of Aviation and Police to ensure that individual employees are not assigned incompatible business functions within the Oracle system. We identified some inconsistencies between the departments’ submissions and current project team designations. We also identified a few employees whose proposed responsibilities could combine incompatible duties.
Review of Incompatible Duties across all Responsibilities within Oracle - April 2008
Our objective in this most recent review was to examine the assignment of users to multiple responsibilities to determine whether the assignments allow users to perform incompatible duties.