The information below is intended to provide colleges guidance on performing a User Acceptance Test on this business process. The business process shown in the flow diagrams below may be only part of what is needed to complete an end-to-end test of a full business cycle. Coordination with other colleagues at your college in advance of commencing testing is key to success. In the same way that it doesn't take a single individual to operate the business of running a college it will require coordination across departments to successfully test a business flow from beginning to end.

Incorporating Data Validation into the Data/Transaction Selection for Executing UAT:

One aspect of a successful User Acceptance Test is understanding how legacy data has been converted and ensuring that colleges have tested data scenarios that use the converted data as part of the test activity.  In this way colleges can test 'real life' situations for things like re-hiring an employee who was separated prior to conversion, but whose data was brought forward into PeopleSoft.  

By including such data scenarios colleges can both ensure they understand how to manage staff who were converted and truly understand how the converted data was moved into PeopleSoft, in case the way the data converted presents a particular problem for the institution.  With this approach, there is time to find such data conditions prior to the final round of conversion, the Dry Run prior to Go Live.

Printable View of HH.001.10 Enter and Process Time Flow Diagram

• HH.001.10.1  Employee Enters Overtime Request
• HH.001.10.2  Manager Evaluates and Acts on Overtime Request
• HH.001.10.3  Employee Enters Time
• HH.001.10.4  Run Time Admin Manually for All Employees
• HH.001.10.5  Manager Evaluates Time Entry
• Repeat HH.001.10.4
• HH.001.10.6  Manager Approves the Time for Employees
• Repeat HH.001.10.4
• HH.001.10.7  Run Batch Approval
• Repeat HH.001.10.4
• HH.001.10.8  Examine Exceptions
• HH.001.10.9  Correct Employee Timesheet to Resolve Exceptions
• Repeat HH.001.10.4
• HH.001.10.10  Adjust Paid Time for Employees

Scenarios for HH.001.10.1 - Employees Enter Overtime Request

• Request Overtime

Scenarios for HH.001.10.2 - Manager Evaluates and Acts On Overtime Request

• Approve requested overtime
• Reject requested overtime

Scenarios for HH.001.10.3 - Employees Enters Time

• Report time as hourly
• Report time as student
• Report time as classified
• Report overtime on a timesheet
• Report comp time accrued on a timesheet
• Report time so an exception generates from the timesheet

Scenarios for HH.001.10.4 - Run Time Admin Manually for All Employees

• Run Time Admin for ALL
• Run Time Admin for one employee
• View exempt time and labor timesheet
• View FTF time and labor timesheet
• View PTF time and labor timesheet

Scenarios for HH.001.10.6 - Manager Approves Time for Employees

• Approve time as a supervisor
• Deny time as a supervisor
• Push back time as a supervisor

Scenario for HH.001.10.7 - Run Batch Approval

• Approve time as an admin (batch approval) for one employee

Scenarios for HH.001.10.8 - Examine Exceptions

• Clear an exception

Scenarios for HH.001.10.9 - Correct Employee Timesheets to Resolve Exceptions

• Adjust an employee's timesheet as an admin or manager

Scenarios for HH.001.10.10 - Adjust Paid Time for Employees

• Make a record only adjustment on an employee 

Using Converted Information to Strengthen Comprehension of Validated Data

Report and Approve Overtime:

• No College in DG4 has opted into this functionality, please do not utilize.

Report and Approve Timesheet Entry:

• Find a Classified employee who was converted with an active job. Perform time entry on their behalf in timesheet. Approve/deny time as employee's manager/admin.
• Find a Classified employee who was converted with an active job. Perform comp time entry on their behalf in timesheet. Approve/deny time as employee's manager/admin.
• Find an Hourly Employee who was converted with an active job. Perform time entry on their behalf in timesheet. Approve/deny time as employee's manager/admin.
• Find an Hourly Employee who was converted with an active job. Perform overtime entry on their behalf in timesheet. Approve/deny time as employee's manager/admin.
• Find a Student Employee who was converted with an active job. Perform time entry on their behalf in timesheet. Approve/deny time as employee's manager/admin.

Process and View Timesheets as an Admin:

• Generate an exception in a Student timesheet by submitting the wrong workstudy code.
• Generate an exception in a Classified timesheet by submitting over 15 total hours in a single day (if it is in your rule program).

Sourcing Data for Converted Information

Not sure how to identify employees that meet the criteria above?  Refer to the Data Validation Guide on Time & Labor data to learn how to run the TL_VAL_TIME_REPORT_ENROLL Query and export a list of converted employees with their job information.

HH.001.10.3 - Employees Enter Time:

• Error Condition: Enter SWS TRC on a FWS student's timesheet.
  • Expected Behavior: Will allow entry of the wrong TRC.  An exception will populate when Time Admin runs.
• Error Condition: Enter 17 hours for a day of work on a timesheet.
  • Expected Behavior: Will allow entry of the wrong TRC.  An exception will populate when Time Admin runs.
• Error Condition: Enter both Comp Time Accrued and Overtime on the same day.
  • Expected Behavior: More than 15 hours in a TRC generates a warning.
• Error Condition: Do an incorrect punch order on a punch time timesheet (In followed by Meal In etc.).
  • Expected Behavior: Both comp time accrued and overtime will save to the timesheet.  There is no validation to prevent it.
• Error Condition: Enter a full day of work on a day when a full absence is reported
  • Expected Behavior: The full day of both  absence and work will save, once both enter payable time (absence only  does so on finalization) then an exception will generate.
• Error Condition: Enter work on the timesheet for an off day according to the schedule.
  • Expected Behavior: OVT and CTE will save regardless of hours entered before.  There is no validation to stop it.
• Error Condition: Put in OVT or CTE before reaching 40 hours in a week
  • Expected Behavior: A single in punch on its own will save.  An in punch followed by another in punch will not process.
• Error Condition: Don't enter an Out time on a Punch time sheet
  • Expected Behavior: Entering time on the  wrong job will save.  Even if the employee enters identical time on both  timesheets, it will save.  There is no validation to prevent it.

UAT HH.001 Hire to Payroll with Centralized Management [Sprint 1]

 HH.001.9 - Enter and Process Absence Takes