Skip to end of metadata
Go to start of metadata

Business Logic

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-317

Business Logic - Weekly Overtime

General logic testing, Cases where FLSA period doesn't match with pay calendar eg. semi monthly pay period.

ISU

(tick)

Test Cases

(error) 12 of 16 Complete

KPME-773

Business Logic - Daily Overtime

 

ISU

(tick)

Test Cases

(tick)

KPME-810

Business Logic - Daily and Weekly Overtime

Daily overtime, overtime, shift and how they work with lunch deduction (reduces hours - therefore not counted in OVT and shift calculation), validate that employees with both daily overtime rule and weekly overtime rule behaves correctly

ISU

(tick)

Test Cases

(error)

KPME-739

Business Logic - Earn Code - Used to define categories by which employees can record their time such as regular earnings, vacation time, overtime etc.

*The open case is tied to a minor jira that has been moved to the 1.0 bucket. The Jira is KPME-903 .

UGA

(tick)

Test Cases

(error) 1 of 13 Still Open

KPME-774

Business Logic - Earn Groups - Used to define logical groupings of earn codes for various uses throughout the system such as how to summarize hours at the bottom of the timesheet

Remaining Jiras are assigned 1.0 release 

UGA

(tick)

Test Cases

(error)  1 of 10 still open

KPME-318

Business Logic - Shift Differential & Premium Pay

Include testing against pay calendars that do not start at midnight

CoB

(error)

Test Cases

(error)

KPME-617

Business Logic - Grace Period - Used to define the rounding rules associated with clock actions both for clock in / out and administrative changes to clock actions.

 

ISU

(tick)

Test Cases

(tick)

KPME-638

Business Logic - Department Earn Code - Used to define the list of available earn codes on a time sheet based on the users role, department, salary group, and location

 

ISU

(tick)

Test Cases

(tick)

KPME-670

Business Logic - System Lunch Rule - Used to define a system level rule as to whether or not a lunch button will be displayed after clocking in. This can be overridden by a department lunch rule

 

CoB

(tick)

Test Cases

(tick)

KPME-693

Business Logic - Time Collection Rule - Used to define work areas as clock in/out, manual entry and other attributes

 

CoB

(tick)

Test Cases

(error) 3 of 5 still open

KPME-701

Business Logic - Clock Location Rule - Used to generate warnings on timesheets for employees that clock in or out of an unapproved IP addressed

 

SJDC

(tick)

Test Cases

(tick)

KPME-711

Business Logic - Department Lunch Rule - Used to generate automatic lunch deductions when employees work a minimum number of hours

 

IU

(tick)

Test Cases

(error) 4 of 8 Complete

KPME-766

Business Logic - Holiday Calendar and Dates - Used to add holiday dates to employee's timesheets

 

ISU

(tick)

Test Cases

(tick)

KPME-775

Business Logic - Accrual Category - Accrual categories are used to define categories of benefit time that employees accrue time against such as Vacation, Sick, etc. Business logic should validate that time entry correctly validates against recording hours against these accruals.

Addition of time to timesheet validates against proper buckets, balances properly displayed, adding time to and from timesheet validates correctly

UGA

(tick)

Test Cases

(tick)

KPME-811

Business Logic - Hours Distribution - Used to allow employees to clock in and out of a single assignment and then distribute hours at the end of the day to multiple assignments

 

ISU

(error)

Test Cases

(error)

KPME-812

Business Logic - Assignment (Work Area + Task) - Used to identify categories for employees to record their time, drives routing and funding.

Assignment show up in the timesheet drop down list, descriptions are correct, change in drop down when changed, only 1 assignment for department, validation to require 1 assignment for the reg earn code for the pay type of the employee (should default in to the funding section on the assignment page). OVT earn code properly assigned, displays the correct descripition

CSU

(tick)

Test Cases

(error)

KPME-813

Business Logic - Pay Calendar - Used to drive the display and boundaries around which timesheet data is recorded.

Setup various calendars and verify represented appropriately on timesheet (Retest - Overtime, shift differential, principal calendar - getting the right one) Times outside of (test around what partner institutions do - sunday midnight, semi monthly)

ISU

(error)

Test Cases

(error)

KPME-814

Business Logic - Pay Type - Used to drive the display of the regular earn code on the timesheet

 

ISU

(error)

Test Cases

(error)

KPME-815

Business Logic - Missed Punch - Used to allow employees to manually record a missed clock action (in or out). Document is created and routed to supervisor for approval

 

ISU

(error)

Test Cases

(error)

KPME-816

Business Logic - Timesheet - Business logic surrounding the use of the main data entry screen for manual time entry

Overnight timeblocks, multiple days, sum of hours, time entry widget, apply time to each day, dates outside of the pay calendar in widget, scrolling prior timesheets ( non editable) - color coding, editing time block, delete time block, can't delete timeblock if clock only, warnings when deleting timeblock, warnings for special earn codes (eg. documentation required for this earn code) need to add , summary weeks match the week rows at the top of the page.

ISU

(tick)

Test Cases

(error)   14 of 16 Complete

KPME-817

Business Logic - Clock Page - Used for clock entry employees to record time worked

time blocks properly created on clock in /out, lunch in out create time blocks appropriately and LO / LI created in clock log, interaction between missed punch and next clock in.

 

(error)

Test Cases

(error)

KPME-818

Business Logic - Timezone - Validate that clock actions and manually entered time properly saves data based on the employees timezone.

location of the job, on location table, adding timezone. Assume the employee is in this timezone, unless override on the principal calendar. Time on clock page matches timezone on the job or override, stores based on the server timezone, displays back based on the offset.

ISU

(error)

Test Cases

(error)

KPME-819

Business Logic - Notes - Verify notes are properly recorded and retrieved when displaying timesheet.

 

IU

(error)

Test Cases

(error)

KPME-589

Business Logic - Work Schedule

 

 

(error)

Test Cases

(error)

KPME-820

Business Logic - Exception Handling/Reporting
 

  1. Add an edit so that with any/every save all assignments are checked to verify still valid.
     
  2. Add logic to the autoapprove job to kick time sheets to exception if invalid assignment (not move them on to the next level).
     
  3. Need warning message on timesheet at routing if time recorded against a pending assignment so the approvers/pay proc will be aware the hrs might not extract if assignment edoc not saved.
     
  4. Add logic to approver tab, if employee clocked in > x hours, turn row red

 

 

(error)

Test Cases

(error)

KPME-821

Business Logic - Timesheet Warnings - Warnings given should remain on the timesheet.  Supervisors/Payroll Proc shld see icon on approver tab adv there is a warning.  Examples of warnings needed: Unapproved Clock Location, Leave Balance Exceeded, FMLA Paperwork required.

 

 

(error)

Test Cases

(error)

Routing and Approval

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-305

Approval Routing - Timesheets have a maximum of three defined approval stops

(1) Employee: will also be the document Initiator in Workflow (2) Supervisor: Workflow Approver (3) TIME Processor: Workflow Final Approver (optional) There are no system limitations which prevents the employee from being their own approver

 

(error)

Test Cases

(error)

KPME-307

Approval Routing - System is configurable so that timesheet is editable by employee until approved by supervisor. Configuration options are, can't edit once submitted vs. can edit until approved by route level 1

 

 

(error)

Test Cases

(error)

KPME-308

Approval Routing - The system will allow auto-approval of all timesheets at a given route level.

For instance, it is not necessary for employees to submit their timesheets – a batch approval job will run when the pay period ends. Another example would be a batch Supervisor approval that would auto-approve any timesheets that supervisors have not approved so that TIME Processors have a chance to approve the document. An annotation is added to the workflow action taken table and shows in the route log.

 

(error)

Test Cases

(error)

N/A

Approval Routing - Rule-based optional FYIs based on routable attributes.

This is an institution implementation specific requirement that requires defining routable attributes.

N/A

N/A

N/A

N/A

Authorization / Authentication

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-302

Authorization - Roles will have labels which are configurable by institution

 

 

(error)

Test Cases

(error)

KPME-303

Authorization - Role Types

  1. Employee Role - has access to their own timesheet. Editing rights when in Workflow Action List only (ie. not submitted for approval)
  2. View Only Role - has ability to open a timesheet from Workflow. No editing or approval rights. Can be set at the Department, Work Area or Global levels.
  3. Reviewer Role - has timesheet editing rights but will not be in the approval chain. Can be set at the Work Area level.
  4. Approver Role - has editing rights and will be the first routing stop. Set at the Work Area level.
  5. Processor Role - has timesheet editing rights and will be the final route stop before transferring data to the KPME Payroll system. Set at the Department level.
  6. Department Adminstrator Role - This allows distribution of certain central-office access to select users and is useful on multi-campus institutions or at institutions with decentralized payroll. Set at the Department level or Chart
  7. System Manager Role - Edit access to all system features. Typically only a few users would have this access. Typically set at the top level department in the org chart. NOTE: Users may be in more than one role so access is limited on two planes: Departmental org structure and KT Role. So if you are a TIME Manager in department A but only a Supervisor in a Work Area for department B, you would NOT have TIME Manager-level rights in department B.
  8. Interface Manager Role - Highest level of access which has all of the access to timesheets, editing, batch job and super user workflow abilites.

Role Security Access defined at Role Security

 

(error)

Test Cases

(error)

Future

Authorization - Roles can be assigned to individuals or Workflow Workgroups.

 

 

(error)

Test Cases

(error)

N/A

Access - Kuali Time and Attendance will be available 24/7/365 to any computer with an internet connection.

This is important to keep in mind when considering the use of other databases for source data (such as HR employment records). These other databases usually have the luxury of being down for maintenance outside of regular business hours so there will need to be some caching/duplication of dependent data. Future: Kuali Time and Attendance will be accessible for time recording from mobile devices

N/A

N/A

N/A

N/A

N/A

Authentication - Users must authenticate through the school’s authentication scheme

Kuali Time and Attendance will not create separate user accounts or store any passwords

N/A

N/A

N/A

N/A

N/A

Authorization - Role based authorization will be configured through maintenance pages

Roles can be managed through different pages depending on the role. Assigning / Managing roles by user id is done in the Role Group Maintenance page. Org Administrator can be done in the Department page. Approver roles can be done in the Work Area page

N/A

N/A

N/A

N/A

Future

Authorization - Roles will be hierarchical and based on the Department/Organization structure in Kuali HR as well as Work Areas defined in the Kuali time and Attendance system.

If a given user has View-Only rights at a Responsibility Center level and four Departments roll up to that RC then the user has view-only rights in all four of those departments (all Work Areas).

N/A

N/A

N/A

N/A

Batch Job Testing

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-587

Batch - Time Sheet Initiate

 

 

 

 

 

KPME-822

Batch - Notifications - Provide the following notifications: "Enter/Verify Hours" notice (last normal work day of pay period), "Pay Period End Reminder" (after pay period is over adv timesheet was routed for approval), "Timesheet has been edited" notice, "Missed Punch Approved"

 

 

 

 

 

Audit Capabilities

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-309

Audit Capabilities - System will record the employees IP address for any clock actions

IP Address is recorded in the clock log table

 

(error)

Test Cases

(error)

KPME-310

Audit Capabilities - Any additions, deletions, or edits to time blocks will record the user’s id, time of edit, and original values

Data recorded in the time block table

 

(error)

Test Cases

(error)

KPME-311

Audit Capabilities - All approval auditing will automatically be captured in Workflow

 

 

(error)

Test Cases

(error)

KPME-312

Audit Capabilities - Rule and maintenance tables will capture a user id and a timestamp for each addition to the table. Entries will have an Effective Date and Active/Inactive flag so that no entry will need to be deleted.

 

 

(error)

Test Cases

(error)

Configuration Setup / Maintenance Tables

NOTE: All maintenance tables have been tested although test scripts for each were not documented. We will circle back around at some point and identify test cases for these pages but at the moment, testing business logic is the priority and issues with individual maintenance pages will likely show themselves when setting up data for business logic testing.

Jira ID

Requirement Description

Notes / Rationale

Assignee

Test Cases Written

Test Cases

Tests Completed

KPME-382

Pay Calendar - The system will allow for the definition of pay calendars to designate the FLSA period start and end times. The system will be configurable to allow one or more of the following pay cycles. Weekly, Biweekly, Semi Monthly, Monthly

Employees will have one timesheet per pay cycle but may have concurrent timesheets in other pay cycles. Overtime, Shift Pay etc. is determined based on a single timesheet

SJDC

 

Test Cases

(tick)

KPME-381

Pay Calendar Entries - The Pay Calendar Entry maintenance page defines the pay period and batch schedule for a pay calendar group. Entries must be created for a time period before a timesheet can be created. Although no batch process is provided, institutions may choose to create a job which populates these values based on their institutions default values. These maintenance pages would then be used to modify any exceptions to the default.

 

SJDC

 

Test Cases

(tick)

KPME-322

Department Maintenance - Allow entry of department level
roles

Roles will traverse the org hierarchy it is not necessary to have each role at every department. One TIME Manager in a large Responsibility Center could administer many departments that roll up to that RC.

 

 

Test Cases

(tick)

KPME-324

Work Area Maintenance - Used primarily to define approval routing under a given Supervisor. Also will some basic rules like time collection method and overtime preference (paid or compensatory time).

Any new work area added will need to be verified for mandatory route stops (Supervisor and TIME Processor). Will also provide a way to add assignments to all users in that work area by providing a valid Account and alternate routing (if needed) per account. This would, for example, allow easy addition of new TIME assignments to a group of research assistants when new grant money was received. Any work logged under that assignment is paid from that account without having to change the employee’s labor distribution in the HR system.

 

 

Test Cases

(tick)

KPME-323

Earnings Maintenance - Controls the display of valid earnings for a particular group of employees. For instance, employees who are not eligible for Vacation accruals should never have that earning as a choice when recording time.

This table will also control the display of available earnings per role so that you can exclude earnings from the employee list that need administrative approval. Would also allow for departments to add/remove earnings as applicable to their specific department (for instance a special shift rate earning that only applies to maintenance employees).

 

 

Test Cases

(tick)

KPME-325

Earnings Group - Create groups of earnings to be used by system rules. Some examples would be defining “regular” pay for meeting a job’s standard hours (FTE) to be made up of Regular Work Hours plus Vacation, Sick, etc. or defining a group of earnings that should display a warning message when used (such as FMLA).

Pulls available earnings from KPME Payroll system.

 

 

Test Cases

(tick)

KPME-326

Weekly Overtime Rule - Provide logic for automatic conversion to overtime (or comp time) when hours worked exceeds some threshold such as 40 for regular overtime. Allows for steps to define where overtime is charged.

Will allow multiple rules to be applied to the same timesheet to accommodated double and triple overtime. Uses Earnings Groups to determine what hours count towards regular hours.

 

 

Test Cases

(tick)

KPME-327

Daily Overtime Rule - To provide overtime pay when policy or law demands overtime compensation on a daily basis. As an example, some union workers may get overtime whenever they exceed the scheduled 8-hour day.

Rule can be set up down to the Work Area level so that only one group in a department may be eligible or you can use wildcards to make it apply to a broader group (including everyone).

 

 

Test Cases

(tick)

KPME-328

Grace Period Rule - Set rounding factor for clock punches.

Allow different rounding rules for different employee types.

CoB

 

Test Cases

(tick)

KPME-329

Department Lunch Deduction - Allow for specified lunch deduction from applicable shift without having the employee clock in and out for lunch.

Rule can be set up down to the employee record or wild-carded for larger groups.

 

 

Test Cases

(tick)

KPME-330

Shift Differential/Premium Rule - Applies specified shift earnings for applicable hours worked within a specified time range.

Rule can be set up down to the Work Area level. Rule can also be used for Premium pay.

 

 

Test Cases

(tick)

KPME-331

Holiday Calendar - Allow for entry of calendar dates and associated Holiday earn code.

Calendar can be used for standard Holiday earnings (single entry) or can be entered as two rules on the same date if your school uses separate ‘accrued’ and ‘taken’ earnings. Can be set to be a factor of FTE. In other words, a rule set up to apply 8 hours of Holiday would only apply 4 hours to a 0.5 FTE job record.

ISU

 

Test Cases

(tick)

KPME-383

System Lunch Rule - System level setting which determines if the “Take Lunch” and “Return from Lunch” buttons display for clock entry employees. If the employee is subject to a lunch deduction rule, no lunch buttons will be displayed.

 

CoB

 

Test Cases

(tick)

KPME-384

Accrual Category - The Accrual Category maintenance page is used to defines the categories (“buckets”) of benefit time employees earn/take. This document strictly establishes the categories (ex: Sick), the “Time off Accrual” document is used to give employees balances in these categories. The maintenance of these balances must occur in another system currently, and the balances are then fed into Kuali Time. Kuali Time only stores the balances for display and edits and does not currently do any calculations. Accruals are to be implemented in the Attendance phase.

 

ISU

 

Test Cases

(tick)

KPME-436

Earn Code- The Earn Code maintenance page is used to define codes to categorize employee’s hours/earnings.

 

 

 

Test Cases

(tick)

KPME-437

Department Earn Code- The Department Earn Code maintenance page is used to define which roles (employee, approver, org admin) see specific earn codes on the timesheet.

 

 

 

Test Cases

(tick)

KPME-438

Pay Type- The Pay Type maintenance page defines a classification of position / job used to divide groups of employees according to payroll attributes.

 

 

 

Test Cases

(tick)

KPME-439

Salary Group- The Salary Group maintenance page is used for classification of jobs / positions into a group.

 

 

 

Test Cases

(tick)

KPME-440

Pay Grade- The Pay Grade maintenance page is used to define a classification of position / job to divide groups of employees for the purposes of defining rules within the Time and Attendance system.

 

 

 

Test Cases

(tick)

KPME-441

Location- The Location maintenance page defines location(s) for an organization and is associated with an employees job.

 

 

 

Test Cases

(tick)

KPME-573

Time Collection Rule - The Time Collection Rule maintenance page is used to define how employees record time, via clock entry or manual entry. This rule can be defined at various levels including at a system level or specific down to an employee. The timesheet shows the clock tab for entry if the most specific rule for that assignment is marked as a clock user.

 

 

 

Test Cases

(tick)

KPME-574

Clock Location Rule - The Clock Location Rule maintenance page is used to define “approved” IP addresses for clock entry. Rules can be set system wide, or as granular as a specific employee job record. The most specific rule for that assignment will be enforced. This rule will not restrict the clock action but will note the timesheet that the clock was from an “unapproved location”. Regardless of a rule, the IP address is captured on every clock action and can be seen in the Clock Log Inquiry page.

 

 

 

Test Cases

(tick)

KPME-575

Account - The Account maintenance page is used to define the "account" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Account is the third level of the organizational division. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-576

Assignment - The Assignment maintenance page is used to define the assignment and funding attributes for a given employees job record. An employee can be given one to many assignments and the funding per assignment must total to 100%. Multiple assignments can be used when the employee reports to different time approvers, or when different accounts should be charged based on the work done. The employee records the hours against assignments. An assignment is a unique combination of job, job number, work area and task.

 

 

 

Test Cases

(tick)

KPME-577

Chart - The Chart maintenance page is used to define the "chart" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Chart is the highest level of the organizational division. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-578

Job - The Job maintenance page is used to associate a person with job attributes. A single person may have multiple jobs and each job can have only one pay rate. Each job can have 1 to many assignments (work areas + tasks) for which they will be able to record their time. Each job for a given employee is assigned a unique job number. Other attributes on the job maintenance page are used to determine which rules to apply. It is likely that these attributes will be mapped to an existing payroll/HR system.

 

 

 

Test Cases

(tick)

KPME-579

Object Code - The Object Code maintenance page is used to define the "object" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Object Code is associated with chart and organization. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-580

Organization - The Organization maintenance page is used to define the "organization" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Chart is the 2nd highest level of the organizational division. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-581

Principal Calendar - The Principal Calendar maintenance page is used to associate a pay calendar and holiday calendar group to an employee. An employee can have only one value for each group.

 

 

 

Test Cases

(tick)

KPME-582

Project Code - The Project Code maintenance page is used to define the "project" component of the chart of accounts and is used to establish funding sources associated with an employee assignment. Project code is an optional component the chart of accounts and is intended to be used to track financial transactions by project across many accounts. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-583

Sub Account - The Sub-Account maintenance page is used to define the "sub-account" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Sub-account is defined as an optional level of accounting detail underneath the account field. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-584

Sub Object Code - The Sub-Object maintenance page is used to define the "sub-object" component of the chart of accounts and is used to establish funding sources associated with an employees assignment. Sub-object is defined as an optional level of accounting detail underneath the object field. All components of the chart of accounts are based on the Kuali Financial System.

 

 

 

Test Cases

(tick)

KPME-585

Time Off Accrual - The Time Off Accrual maintenance page is used to create and maintain balances in the accrual categories for an employee. Hours Accrued - Hours Taken + Hours Adjusted = Available Balance. This available balance is displayed on the “Leave Accrual” tab in the timesheet and is used to validate that balances are not exceeded when entering earnings codes that are attached to a given accrual category. Kuali Time and Attendance does not currently calculate accruals, therefore these balances are held strictly for validation of usage and display.

 

 

 

Test Cases

(tick)

KPME-823

Work Schedule - The Work Schedule page ......

 

 

(error)

Test Cases

(error)

N/A

Pending job data changes (including hires, transfers) should be pulled into the time system. 

This will allow pending hires to clock in prior to the eDoc being finalized.

N/A

N/A

N/A

N/A

  • No labels
Page: Role Security Grid Page: Test Cases - Approval Routing Auto Approval Page: Test Cases - Approval Routing Employee editable until approval Page: Test Cases - Audit IP Address Page: Test Cases - Audit Rules and Maintenance Tables Page: Test Cases - Audit Timeblock Modifications Page: Test Cases - Audit Workflow Approvals Page: Test Cases - Authorization Role Types Page: Test Cases - Business Department Lunch rule Page: Test Cases - Business Logic Accrual Category Page: Test Cases - Business Logic Assignment Page: Test Cases - Business Logic Clock Location Rule Page: Test Cases - Business Logic Clock Page Page: Test Cases - Business Logic Daily and Weekly Overtime Page: Test Cases - Business Logic Daily Overtime Page: Test Cases - Business Logic Department Earn Code Page: Test Cases - Business Logic Earn Code Page: Test Cases - Business Logic Earn Group Page: Test Cases - Business Logic Exception Handling and Reporting Page: Test Cases - Business Logic Grace Period Page: Test Cases - Business Logic Holiday Calendar and Dates Page: Test Cases - Business Logic Hours Distribution Page: Test Cases - Business Logic Lunch Deduction Page: Test Cases - Business Logic Missed Punch Page: Test Cases - Business Logic Notes Page: Test Cases - Business Logic Pay Calendar Page: Test Cases - Business Logic Pay Type Page: Test Cases - Business Logic Shift Differential and Premium Pay Page: Test Cases - Business Logic System Lunch Rule Page: Test Cases - Business Logic Time Collection Rule Page: Test Cases - Business Logic Timesheet Page: Test Cases - Business Logic Timesheet Warnings Page: Test Cases - Business Logic Timezone Page: Test Cases - Business Logic Weekly Overtime Page: Test Cases - Business Logic Work Schedule Page: Test Cases - Maintenance - Accrual Category Page: Test Cases - Maintenance - Daily Overtime Page: Test Cases - Maintenance - Department Page: Test Cases - Maintenance - Department Earn Code Page: Test Cases - Maintenance - Department Lunch Page: Test Cases - Maintenance - Earn Code Page: Test Cases - Maintenance - Earnings Page: Test Cases - Maintenance - Earnings Group Page: Test Cases - Maintenance - Grace Period Page: Test Cases - Maintenance - Holiday Calendar Page: Test Cases - Maintenance - Location Page: Test Cases - Maintenance - Pay Grade Page: Test Cases - Maintenance - Pay Type Page: Test Cases - Maintenance - Salary Group Page: Test Cases - Maintenance - Shift Differential Page: Test Cases - Maintenance - System Lunch Rule Page: Test Cases - Maintenance - Weekly Overtime Page: Test Cases - Maintenance - Work Area Page: Test Cases - Pay Calendar Page: Test Cases - Pay Calendar Entries Page: Test Cases - Pay Cycle Page: Test Cases - Pay types Page: Test Cases - Rule Based FYI Messages Page: Test Cases - Time Collection