DOCX

Upgrade System Test Approach

By Kathy Flores,2014-04-01 19:17
12 views 0
Upgrade System Test Approach

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

Parallel Test Approach

I. Introduction

    The purpose of this document is to explain the approach that will be used for a Parallel Test phase of the University of Michigan HE Upgrade Project. This document outlines the following:

    ; Parallel Test objectives and scope

    ; Parallel Test comparison tools

    ; Parallel Test entry and exit criteria

    ; Parallel Test calendar

    ; Parallel Test team

    ; Parallel Test issues and risks

    ; Parallel Test issue resolution process

    ; Parallel Test assumptions

II. Parallel Test Approach

A. Objectives

    The primary objective of Parallel Test is to identify discrepancies in the Gross-to-Net calculation between versions of Michigan’s PeopleSoft system. All data will have been

    entered using the PeopleSoft system and will have been converted into the Parallel environment via the conversion script to be used for production implementation (no conversion from legacy data is required).

    Table 1 includes the components of the gross to net calculation that may cause discrepancies between paychecks created in the v7 PeopleSoft Payroll System and paychecks created in the v8 PeopleSoft Payroll System. The parallel testing process tests these components and resolves any discrepancies between the two. Resolutions may come in the form of:

    ; Updating software configuration

    ; Correction of work units (e.g. fixing custom programs that impact gross-to-net)

    ; PeopleSoft correcting delivered source code

    ; Correcting data conversion scripts

    ; Explaining and accepting the discrepancy.

    374523658.docx Page 1 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

    Other normal biweekly and monthly processes will be run and results checked, but will not be compared against production data. E.g. Paycheck distribution, gross pay register, G/L interface, leave accrual, etc.

Table 1

    Gross Earning Calculations verifying the employee’s gross earnings tests the following:

    ; delivered/upgraded gross earning calculation routines correctly calculate an

    employee’s gross pay

    ; modified/custom gross earning calculation routines correctly calculate an

    employee’s gross pay

    ; earnings table is set up correctly

    Deduction and Garnishment Calculations verifying the employee’s deductions and

    garnishments tests the following:

    ; delivered/upgraded deduction and garnishment calculation routines correctly

    calculate all types of deductions (e.g., before tax, after tax, employer paid, etc)

    ; modified/custom deduction and garnishment calculation routines correctly calculate

    all types of deductions

    ; deduction table is set up correctly

    ; garnishment rule and disposable earning definition tables are set up correctly

    ; benefit plans and benefit programs are set up correctly

    Tax Calculations verifying the employee’s taxes tests the following:

    ; delivered/upgraded tax calculation routines correctly calculate federal, state, and

    local taxes

    ; modified/custom tax calculation routines correctly calculate federal, state, and local

    taxes

    ; federal, state, and local tax tables are setup correctly

    Time & Labor verifying the loaded time data tests the following

    ; delivered/upgraded Time Admin process correctly loads time into the system

    ; modified/custom Time Load Interface correctly loads time into the system

B. Scope

In order to fully test Michigan’s Gross-Net-Calculation for both of its pay frequencies,

    five separate parallel tests will be executed. Parallel testing uses historical payroll data from the current version of the PeopleSoft Payroll System. In other words, prior to the start of parallel test, the pay periods have already been processed in the Payroll System. First, this allows the parallel test team to extract the historical payroll data and prepare it for comparison to PeopleSoft data without interfering with the current production system’s operations. Second, flexibility is built into the parallel test schedule because it is not dependent on the production system’s payroll processing schedule.

    374523658.docx Page 2 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

    The parallel test will not test each employee in the system, since doing so would require replication of manual keypunching done by timekeepers. Instead, a cross-section of employees has been chosen, which will include most of the University’s employees. The employees in parallel test will meet one of the following conditions:

    1) Loads to Time and Labor via interface file (including Corpay scanned

    timesheets, as well as interfacing departments).

    2) Does not exist in Time and Labor.

    3) Is in workgroup PAEXHOSP. This workgroup includes many MPP employees,

    most of which are not eligible for TRCs such as Overtime or Shift, which would

    affect their Net Pay. Even though their time will not be loaded into Time and

    Labor, this should not affect their pay.

    The Parallel Test will load Convenience Deduction data. Cycle 4 will include manual changes made to paysheets, since Payroll Office staff will perform dual entry for these changes in the Cycle 4 parallel tests. BWR employees will only be tested in Cycle 1.

    Prior Period adjustments will not be tested in Parallel test; they will be included in System Test. System Test will also test keypunch data entry through the payroll cycle.

    HE 8.0 Upgrade Parallel Test Scope

    Cycle 1

    Time LoadTime AdminCycles 2, 3, 4Time filesInterfaceappengine

    PayPrintDirectPaysheetPaycalcConfirmPaychecksDeposit

    G/L InterfaceSponsoredResearch

374523658.docx Page 3 of 13 Last Updated - 4/1/12

    Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

    C. Parallel Test Cycles: The following test cycles have been defined for

    Parallel Testing

    o Cycle 0 Mock Parallel

    ; Verify that PARA(for new PS version) has been setup correctly,

    and that programs/tables/data have been migrated completely.

    Data will not be reconciled at this point.

    ; Should be completed prior to “real” start of Parallel Test.

    o Cycle 1 Biweekly without Time Load

    ; XX/XX/XX pay period end date

    ; Based on date of production cut of data, Time WILL already have

    been loaded into payroll; so custom Time interface WILL NOT

    need to be run.

    ; Verify that Payroll-only functionality has not been adversely

    affected by upgrade.

    o Cycle 2 Biweekly with Time Load

    ; XX/XX/XX pay period end date

    ; Based on date of production cut of data, Time will NOT have been

    loaded into payroll; so custom Time interface WILL be run.

    ; Verify that T&L functionality, in addition to payroll, has not been

    adversely affected by upgrade.

    o Cycle 3 Monthly with Time Load

    ; XX/XX/XX pay period end date

    ; Based on date of production cut of data, Time will NOT have been

    loaded into payroll; so custom Time interface WILL be run.

    ; Includes G/L interface, and sponsored research.

    ; Verify that the upgrade did not adversely affect Monthly pay

    processing.

    o Cycle 4 AFTER NEW CUT OF PRODUCTION DATA (from XX/XX/XX

    to XX/XX/XX) AVAILABLE

    ; Re-run Cycle 2 (Biweekly with Time Load) for XX/XX/XX pay

    end date for Biweekly

    ; Re-run Cycle 3 (Monthly with Time Load) for XX/XX/XX pay

    end date for Monthly

    ; Central Payroll and Hospital Payroll offices to assist in reviewing

    and verifying results.

    374523658.docx Page 4 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

D. Parallel Test Comparison Tools

    The Parallel Test Comparison Toolset is a set of PeopleSoft queries, on-line objects, and SQR’s that compare the Gross-to-Net calculation between v7 PeopleSoft Payroll system and v8 PeopleSoft Payroll system. These queries, on-line objects, and SQR’s will be

    created during the Parallel Test Planning and Prep phases to meet Michigan’s requirements. A DB Link between the Production environment and Parallel environment will be created for this purpose.

    There following Parallel Test Comparison Tools created for this effort:

    ; Check Payable Time Query

    ; Gross to Net Comparison Report with Earnings/Deductions/Taxes Detail Check Payable Time Query

    This query will validate the data in TL_Payable_Time (V8) against the Tl_Empl_Dlyerns and Tl_Empl_Dlysum (V7) after the Time Administration and Load Time and Labor is run. This Query will print only the discrepancies between V8 and V76 data into an Excel Spread Sheet. This will help isolate data errors resulting from the Time & Labor process, which can then be corrected prior to the start of payroll processing. Gross to Net Comparison Report

    This SQR will create a detailed comparison report of the differences between v8 and v7. The program will first compare the net pay amounts in each system. If a discrepancy exists, total earnings, total deductions and total taxes will then be compared. If either of those components does not match in both environments, a detailed listing of records will be written from each system. The resulting report will be an Excel spreadsheet to allow for quick and easy sorting and searching and resolving discrepancies.

The following fields (order TBD) will be included:

    Employee ID

    Paygroup

    Department Code

    Pay Period Begin and End Dates

    Total Earnings, Deductions, Taxes, Gross Pay, Net Pay from v8

    Total Earnings, Deductions, Taxes, Gross Pay, Net Pay from v7

    Total Earnings, Deductions, Taxes, Gross Pay, Net Pay Differences

    Earnings Detail

    The following fields (order TBD) will be included:

    Employee ID

    Paygroup

    Department Code

    Pay Period Begin and End Dates

    374523658.docx Page 5 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

    Earning Codes and Amounts Differences between v8 and v7 Deduction Detail

    The following fields (order TBD) will be included:

    Employee ID

    Paygroup

    Department Code

    Pay Period Begin and End Dates

    Deduction Codes and Amount Differences between v8 and v7 Tax Detail

    The following fields (order TBD) will be included:

    Employee ID

    Department Code

    Pay Period Begin and End Dates

    Tax Codes and Amount Differences between v8 and v7 374523658.docx Page 6 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

E. Entry and Exit Criteria

    Parallel test entry criteria define the tasks that must be satisfied before parallel testing can be efficiently executed. Parallel test exit criteria define the successful conclusion of the parallel testing stage.

    Entry Criteria

    If one or many of these tasks are not complete, parallel test can not begin and the start date will be delayed which may delay the parallel test completion date and ultimately the overall conversion date. Table 2 defines the parallel test entry criteria. Table 2

    1) The Parallel Test environment is established for sole purpose of parallel test and includes all

    custom objects.

    2) The control tables are loaded into the parallel test environment.

    3) Potential “CPU-hog” programs have been tuned to run as efficiently as possible: Interface

    Load Time, Time Admin, etc.

    4) The parallel test team members have been identified and have dedicated time to work on

    the parallel test effort.

    5) The parallel test team has access to the TI Resolution team. Discrepancies will arise that

    require PeopleSoft COBOL, SQR, and Online knowledge and fixes need to be completed in a

    timely fashion to keep parallel test on schedule.

    Exit Criteria

    Parallel test is not complete until all of the exit criteria have been satisfied. If any of the parallel test exit criteria are not satisfied, unexplained discrepancies may exist in the parallel test employee population’s gross to net calculation. As a result, the parallel test team will not have the data that it needs to contribute to the “go live” decision. Table 3 defines the parallel test exit criteria.

    Table 3

    1) All discrepancies have been explained or corrected, and documented.

    2) All earnings calculation discrepancies have been explained or corrected, and documented:

    3) All deduction and garnishment calculation discrepancies have been explained or corrected

    and documented.

    4) All tax calculation discrepancies have been explained or corrected and documented.

374523658.docx Page 7 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

F. Parallel Test Calendar

    The parallel test calendar shows the cycles and schedule (HE 8.0 Upgrade Parallel Test Schedule.xls)

    5/266/26/96/166/236/307/77/147/217/288/48/118/188/259/19/89/159/229/2910/610/1310/2010/2711/311/1011/17MOCK PARALLEL - 3 wks

    biweekly, monthly, time load

    REFRESH ENVIRONMENT

    CYCLE 1 - 3 wks

    12/27/02 biweekly, no time load

    CYCLE 2 - 3 wks

    1/10/03 biweekly + time load

    Apply Tax Update 02-G

    CYCLE 3 - 3 wks

    1/31/03 monthly + time load, G/L, sponsored research

    TEST MOVE #3, new data from 7/31/03 for Parallel Test

    Parallel Resources move to Systest

    Apply Tax Updates thru 7/31 Prod

    CYCLE 4.2 - 3 wks

    re-run cycle 2 for 8/8/03 biweekly

    CYCLE 4.3 - 3 wks re-run cycle 3 for 8/31/03 monthly

    Apply remaining Tax Updates374523658.docx Page 8 of 13 Last Updated - 4/1/12

Information and Technology Services

    PeopleSoft Upgrade Project

    M 5000A2 Parallel Test Approach Document

G.