State of Connecticut
Core-CT Project
Application:HRMS
Module:Payroll
Business Process:Maintain Employee Payroll Data
Requirement Number:PY060
Requirement Title:Create Audit Records to track data changes and inserts
Module Leads: Nancy Ribes, Josh Woodrum
- Requirement Description
Describe the requirement (gap). Include a description of the delivered PeopleSoft functionality.
In the current MSA legacy system, there are audits set up on the majority of the payroll tables in the system. These tables are essential in determining the timing of payroll transactions, as well as for investigating errors or miscalculations that have may occurred in the payroll process. Audit records will need to be created in the PeopleSoft system to track changes that are done by either batch or online entry (depending on preference chosen). Certain types of transactions, specified fields, or all transactions can be set up to be audited on a given record. There are a few records that are delivered with Audit Records in PeopleSoft and the records that require audit should be identified among other tables in the system. A few that should be set up with Audit records include the Job, Additional Pay Data, and Pay One-Time records. For rows that are added into the system, the new fields will be displayed, but for corrected rows the previous value (before the correction) of the fields will be displayed for comparison purposes to the row in the table. Delivered fields such as Operator ID, Action Stamp, and Action are used to display the user that made the change, the time the change was made, and if the row was an insert, correction, deletion, key change, etc.
- Business Need
Provide a justification for the requirement. Include information about frequency, volume, number of users impacted, etc.
This modification will allow users with access to view the Audit data to obtain an accurate history of when changes were made and by which user. This will assist in tracking down if there are practices that are not being followed by users of the system, and allow for a given Operator ID to be identified concerning a given change. Also, audit records give a better understanding of how a given row of data has been manipulated throughout the history of the row, as each change that is made will be tracked in the system.
- Required By: (Y/N)
Federal _N___Agency __N__Bargaining Unit __N__
State Statutory _N___State Regulatory __N__State Procedural __N__
- Requirement Priority
_Medium__(High, Medium, Low – please see “Requirements Prioritization Criteria”)
- Recommended Solution
Enter an “X” next to the appropriate category
______Process Solution
___Option Number
___X___Application Modification
_1__Option Number
- Explanation for Recommendation
Provide reasons for recommendation. Please do not re-state the description of the solution itself.
This modification will allow for quick analysis as to the history of changes made in the system, and how the rows that are audited were entered into the system, at what point they were entered, and who is responsible for entering the row.
- Organizational Impact of Recommendation
Describe the changes to the organization that result from the recommended solution. Include a description of any role, process, statute, or bargaining unit agreement affected.
None.
- Process Solutions
Describe the possible Process Solutions. Include a description of impacts and benefits of each solution.
Option 1. None.
- Application Modifications
Describe the possible Application Modifications. Include a description of impacts and benefits of each solution.
Option 1.
Modification Type (On-line, Batch, Interface, Report, Workflow): On-line and batch
Complexity (Easy, Medium, Difficult): Easy
Description: Audit records need to be created to track the changes, inserts, and deletions into the system on certain tables that are identified to be audited. The fields that are typically added to the audit records are the Operator ID, Action Stamp, and Action type (Insert, Correction, Deletion, Key Change, etc.)
1 of 209/14/18