Code: TECHNICAL LETTER HR/EHDB 2015-03Office of the Chancellor 401 Golden Shore, 4th Floor Long...

Office of the Chancellor 401 Golden Shore, 4th Floor

Long Beach, CA 90802-4210 562-951-4411

Email: [email protected]

Date: September 29, 2015 Code: TECHNICAL LETTER

HR/EHDB 2015-03

To: Human Resources Officers Payroll Managers

From: Evelyn Nazario Theresa Hines Associate Vice Chancellor Director, HRPPDOS Human Resources Management Human Resources Management Subject: Disaster Recovery Testing: October 2015 Applications Testing Reminder

Colleagues:

The enclosed information is provided in support of an annual testing requirement conducted by the State Controller’s Office (SCO.) Disaster Recovery Testing is conducted in efforts to manage risks and maintain business continuity in the event a natural disaster occurs that would disrupt normal payroll-related operations. Systemwide Human Resources Management (HRM) coordinates this testing requirement and ensures that campuses are able to successfully connect with the SCO in order to run tests on certain payroll-related applications. We appreciate the continued participation of campuses as we continue to run these testing requirements on a cyclical basis. Technical letter HR/EHDB 2015-02 is attached for your reference. Please feel free to contact us if you have any questions or concerns. Warm regards, Evelyn and Theresa

mailto:[email protected]

http://www.calstate.edu/HRAdm/pdf2015/TL-EHDB2015-03.pdf

Office of the Chancellor 401 Golden Shore, 4th Floor

Long Beach, CA 90802-4210 562-951-4411

Email: [email protected]

Distribution: CSU East Bay President All Campus Vice Presidents Cal Maritime Academy President State Controller’s Office/Information Systems Division Vice Chancellor, Human Resources

Date: September 29, 2015 Code: TECHNICAL LETTER HR/EHDB 2015-03 To: Payroll Managers Reference1: HR/Salary 2014-25

Human Resources Officers HR/Salary 2014-19 HR/Salary 2013-14

From: Evelyn Nazario Theresa Hines

Associate Vice Chancellor Director, HRPDOS Human Resources Management Human Resources Management

Subject: Disaster Recovery Testing: October 2015 Applications Testing Reminder

Summary To maintain preparedness in the event of a disaster that could potentially disrupt campus payroll-related operations, the Disaster Recovery Applications Testing requirement for campuses on the October annual testing cycle has been scheduled during the week of October 12-16, 2015. Campuses will begin testing on Wednesday, October 14, 2015. This annual testing requirement is conducted through the State Controller’s Office (SCO) and facilitated by the HR Data Operations unit within Systemwide Human Resources Management. The purpose of this technical letter is to remind affected campuses of their responsibilities pertaining to the Applications Testing requirement. Action Item(s): Campuses assigned to the October 2015 testing period are reminded to review the enclosed instructions in preparation for the Applications Testing. Campus designees responsible for facilitating Disaster Recovery Applications Testing should review the remainder of this technical letter for further information. Affected Employees Groups(s)/Units: Campus testing coordinators/designees assigned to this requirement. Overview: HR Data Operations works in collaboration with the SCO to implement testing procedures which will allow campuses to run SCO applications in the event of a disaster that could potentially disrupt campus payroll-related operations. Campuses test annually in the Spring (April/May) or Fall (October) to maintain preparedness. October 12-16, 2015, has been scheduled by the SCO for Applications Testing. Campuses will begin testing Wednesday, October 14, 2015 at 8:00 a.m., testing will conclude on October 15, 2015. Any issues that surface during the testing phase must be resolved by 3:00 p.m. October 16, 2015. A teleconference

1 Information pertaining to Disaster Recovery Applications Testing is more appropriately issued under the Employment History Database (EHDB) category of technical letter coded memoranda. The purpose for this reference footnote serves to identify Disaster Recovery Testing communications that were previously issued under the Salary category of technical letter coded memoranda.


TECHNICAL LETTER HR/EHDB 2015-03

Page 2 of 3

with HR Data Operations has been scheduled for Wednesday, October 7, 2015, from 10:00 a.m. to 11:00 a.m., to answer any questions campuses may have prior to the testing date.

Details pertaining to the Applications Testing requirement are provided in the following attachments:

Attachment A: Business Process Guide: Disaster Recovery Testing for SCO Applications

Testing Attachment B: Campus Disaster Recovery Applications Testers Form Attachment C: Creating A Passport Shortcut to the Disaster Recovery System Attachment D: OTech Disaster Recovery (DR) Test Script (Note: Script updates may be

provided to test coordinators prior to the test period.) Attachment E. Campus Test Coordinators List

Verification of Campus Test Coordinators Campus test coordinators work with the HR Data Operations unit to coordinate testing activities. Test Coordinators are listed in Attachment D. Campuses are requested to review Attachment D and notify HR Data Operations immediately if there has been a change to the campus testing coordinator(s), if applicable (contact: [email protected].) The HR Data Operations unit will provide additional details pertaining to the Applications Testing with the campus test coordinators. As a reminder, the campus test coordinator must have the following qualifications:

Working knowledge of SCO payroll and employment database applications (e.g., CIRS, PIMS, HIST, KEYM, PIP, MPC, IDLS, VIEW, and FTP)

Is a CIRS Security Coordinator or a current security authorizer of SCO applications (form PSD125A)

Campuses Assigned to the October Annual Testing Cycle:

Channel Islands Pomona

Dominguez Hills Sacramento

Fresno San Diego

Los Angeles San Francisco

Maritime Academy San Jose

Monterey Bay Stanislaus

Teleconference Scheduled for October 7, 2015, 10:00 – 11:00 a.m. A teleconference with HR Data Operations has been scheduled for Wednesday, October 7, 2015, from 10:00 a.m. to 11:00 a.m. The purpose of the teleconference is to provide test coordinators with further information in preparation for the October 14-15, 2015 Applications Testing and to answer any questions that participating campuses may have prior to the testing date. All campus testing coordinators are welcomed to participate on the call:

Date: Wednesday, October 7, 2015 Time: 10:00 a.m. to 11:00 a.m. Number: (888) 337-0215 Access Code: 6362295



Page 3 of 3

Questions regarding this coded memo communication should be directed to Systemwide Human Resources at (562) 951-4411. This document is available on the Human Resources Management’s website at http://www.calstate.edu/HRAdm/memos.shtml.

EN/DTH Attachments

http://www.calstate.edu/HRAdm/memos.shtml

Business Process GuideDisaster Recovery Testing for SCO

Applications II: Applications Testing

Last Revised: SEPTEMBER 2015

Disaster Recovery SCO Applications II: Applications Testing Business Process Guide TECHNICAL LETTER HR/EHDB 2015-03 ATTACHMENT A

Last Revised: September 2015

Table of Contents

Page

Revision Control ............................................................................................................................................ iii

Introduction ................................................................................................................................................... iv

Background on the Disaster Recovery Testing for SCO Applications Project .............................................. 1

Purpose of the Project ........................................................................................................................ 1

Approved Recommendation to Conduct the Disaster Recovery Applications Testing ...................... 1

Stakeholders ................................................................................................................................................. 2

Project Sponsors ...................................................................................................................... 2

Roles and Responsibilities ............................................................................................................................ 3

Overview of Required Steps with Forms ....................................................................................................... 4

Process Prerequisites/Assumptions ............................................................................................................. 5

Details of Required Steps for Disaster Recovery Applications Testing ........................................................ 6

Step 1: Complete Required Documentation – Campus action required ............................................ 6

Step 2: Set Up Shortcut on Testers’ Machine .................................................................................... 6

Step 3: Perform Applications Testing – Campus action required ....................................................... 6

Step 4: Notify HR Data Operations of Test Completion Activities – Campus action required ........... 6

Appendix A: Disaster Recovery Applications Testing – Campus Cycles ..................................................... 7

Appendix B: Frequently Asked Questions (FAQ’S) ..................................................................................... 8



Revision Control

Document Title:

Business Process Guide: Disaster Recovery SCO Applications II: Applications Testing

Author: HR Policy and Programs, Data Operations and Systems (HRPPDOS)

File Reference: Disaster Recovery - Applications Testing for SCO Applications Process Guide

Date By Action Pages

04/11/2013 HRM Initial document created All

10/1/2013 HRM Document revised All





Review/Approval History

Date By Action Pages

2/14/2014 DR Project Team, HRM

Approved All

9/25/2014 DR Project Team, HRM

Approved All

9/25/2015 HRM Approved All



Introduction The Disaster Recovery Testing for SCO Applications Project Business Process Guide provides an overview of Disaster Recovery Testing for the State Controller’s Office (SCO) Applications Project and instructions on what is needed for the Disaster Recovery Testing for SCO Applications process at the campus level. When the project was implemented in 2014, Part I covered the first phase of testing (connectivity testing), and Part II addressed applications testing, now an annual testing requirement. The one-time-only connectivity testing phase was successfully conducted at each campus. The purpose of this test was to confirm that the campus’ network and software were configured correctly. Campuses logged onto the Disaster Recovery System to confirm that they were able to successfully connect. This testing phase concluded in October 2013. Campuses proceeded to applications testing in 2014. As part of the Disaster Recovery process, applications testing requires campuses to run applications and perform CIRS functions to ensure that applications are running appropriately under specific test situations. Implementation on this phase of testing was successfully completed in May and October 2014. Applications testing is conducted annually on a Spring (April/May), or Fall (October), cycle by the respective campuses in order to maintain preparedness should an incident occur at the Office of Technology Services (OTech) that could potentially disrupt campus payroll-related operations. The intent of this document is to provide CSU campuses with the established requirements and steps needed to successfully start Disaster Recovery Part II, the applications testing.


Last Revised: September 2015 Page 1 of 8

Background on the Disaster Recovery Testing for SCO Applications Project

Purpose of the Project

The purpose of this project is to test all SCO applications at the disaster recovery site in Vacaville in the event of a disaster that renders all or part of the equipment and data located at Office of Technology Services (OTech) Gold Camp data center, located in Rancho Cordova, inoperable. Twice annually, OTech conducts a disaster recovery test at the OTech Vacaville test site, typically beginning on a Wednesday with data as of the previous Monday. The data, programs, and applications (e.g., CIRS, PIMS, HIST, KEYMASTER, PIP, MPC, VIEW, FTP, and IDLS) are replicated at the Vacaville backup site. Campuses should test to determine whether all critical SCO applications work at the Vacaville site in the same way they do at the OTech Gold Camp production data center. Taken into consideration that the mainframe at the disaster recovery site is smaller than the production machine, online response and batch jobs can take longer than they would in production. To the extent that they do not work correctly, OTech, SCO, and HR Data Operations will have to fix the process so that everyone will be prepared and capable of accessing the backup site in the event of a disaster. Currently if a disaster occurs, it could take up to six months to find a site and construct a new data center. By participating in the Disaster Recovery Testing, campuses will be assured that they will be able to access all SCO applications within one day.

Approved Recommendation to Conduct the Disaster Recovery Applications Testing

After careful consideration of the consequences and in the event a disaster results in the disruption of network activities, the Project Team concluded that the testing project was necessary to prepare stakeholders in the event of such an occurrence. The Project Team recommended that the CSU proceed in dividing the Disaster Recovery testing into two phases:

Phase One: A one-time Connectivity Test. The testing model was distributed to campuses in September 2013, and the Connectivity Test was completed in October 2013.

Phase Two: Applications Test. The initial Applications Testing model was made available to twelve (12) campuses in May 2014. Remaining campuses continued the test in October 2014. Following the successful completion of the initial Applications Testing, the test will be ongoing, to be completed annually by each campus. Participation in the Applications Testing is mandatory for all campuses.

The Long Beach campus and the Chancellor’s Office Human Resources groups served as pilots to test and establish a Disaster Recovery model.



Stakeholders Disaster Recovery testing project requirements were developed based upon input and recommendations provided by the Project Team and stakeholders. Following successful implementation of the project, the Project Team disbanded in 2014. Current stakeholders are noted below:

OTech:

o Provide testing schedule dates

o Provide list of Campus IP address used by the SCO to allow access to the Disaster Recovery network

SCO Information Systems Division (ISD):

o Two months prior to the Disaster Recovery test, SCO will provide HR Data Operations with documentation concerning the dates, goals and objectives, and other documents that are primarily for the SCO

o One month prior to testing, SCO will provide an email confirming the dates, and include the SCO’s staff coordinator listing

Human Resources Management, HR Data Operations unit, Chancellor’s Office:

o Provide initial campus feedback and documented project requirements

o Provide Disaster recovery test scripts

o Provide IP address list for each campus (note: this list will only need to be updated if there is a change in IP address at the campus.)

o Provide IP address information for FTP functionality

o Provide IP address information for Printer functionality

Project Sponsors

Systemwide Human Resources Management



Roles and Responsibilities

Several roles are involved in the successful completion of the campus Disaster Recovery Applications Testing for SCO Applications. The respective roles and typical responsibilities of all parties involved are noted below:

OTech/California Office of Technology Services

Supplies IP addresses and port numbers for campuses.

Manages the Disaster Recovery site.

Chancellor’s Office/Systemwide Human Resources Management/HR Data Operations unit

Oversees the project. Works with testers and campus desktop support. Acts as liaison for OTech and SCO staff in coordinating and overseeing project activities.

Maintains the Campus Disaster Recovery Testers form for each campus.

CSU Campuses

Campuses should designate a Test Coordinator who will oversee the Applications Testing for the campus. This representative will be responsible for interactions and communications with the Disaster Recovery Project Team. This individual will also be responsible for conducting the Applications Testing at campuses. Below are the typical responsibilities for each area at the campus level:

Campus Test Coordinator: Identifies campus system users with access to SCO applications and provides a list of SCO applications the campus will test (e.g., CIRS, PIMS, HIST, KEYMASTER, PIP, MPC, VIEW, IDLS, and FTP). Determines if the campus wants to test printing and FTP. Conducts the Applications Testing at the campus and if testing is assigned to other individuals, manages these tests and reports results to HR Data Operations.



Overview of Required Steps with Forms

Below is a list of required steps for the campus Disaster Recovery Testing along with the responsible parties:

Action Responsible Party

1. Complete required forms and submit to HR Data Operations:

Applications Testing Form (Attachment B).

Campus

2. Submit Firewall Access Form to SCO.

HR Data Operations

3. Setup shortcut for PassPort to point to the logon screen for Disaster Recovery.

In order to test print functionality, the campus will need to set up print sessions that point to the DR server (see Attachment C).

Campus

4. Send out Disaster Recovery scripts, documentation, and instructions.

HR Data Operations

5. Campuses conduct the Applications Testing by following the test scripts in the SCO Applications Instructions and complete the “Actual Results” column in the SCO Applications Instructions document.

Campus

6. Submit test results to HR Data Operations via email.

Campus

7. HR Data Operations informs SCO staff, and completes a Test Results Report and Improvement Plan.

HR Data Operations



Process Prerequisites/Assumptions

Prerequisite/Assumption Detail

SNA/IP Project has been completed at testing campus

The SNA/IP process must be completed at the campus in order to participate in the DR process.

Shortcut for Emulation software; Passport, Attachmate, etc., was created at testing campus

Testers should already have the shortcut to the DR site on their system. If there are new testers, it will be necessary to set up the shortcut on their system.

Connectivity testing was successful at the campus

All campuses successfully tested connectivity in October 2013. If however, any major changes to the campus network occurred since that time, (e.g., change in your campus’ IP address), HR Data Operations will need to be notified in order to update the Firewall Request form.



Details of Required Steps for Disaster Recovery Applications Testing

Step 1: Complete Required Documentation – Campus action required

This step is to be performed by each campus.

The following documentation will need to be completed and submitted to HR Data Operations.

Applications Testing Form (Attachment B).

Step 2: Set Up Shortcut on Testers’ Machine

This step is to be performed by campus IT services. Once the list of campus testers and applications to be tested is reviewed and approved by the appropriate OTECH and SCO staff, campuses will set up the shortcut to the Disaster Recovery system. (note: No need to duplicate this activity if this step has been completed by the campus.)

Step 3: Perform Applications Testing – Campus action required

This step is to be performed by each campus in coordination with the OTECH analysts and/or appropriate SCO staff. On the specified date of the Applications Testing, testers will see if they can log on to each SCO application, and run through their test script. Any problems experienced during the testing period will be reported to the HR Data Operations via:

CIRS Hotline: (916) 323-5694 Gene Howard: (916) 327-6883 Jerry Wakayama: (916) 322-1147

Step 4: Notify HR Data Operations of Test Completion Activities – Campus action required

This step is to be performed by the campus.

At the end of the campus test cycle, an email should be sent to advise testing completion and activities performed to HR Data Operations, Gene Howard ([email protected]) and Jerry Wakayama ([email protected]).

A sample email is provided for reference: To: Jerry Wakayama – [email protected] and Gene Howard – [email protected] Re: <Campus Name> – Disaster Recovery Testing Completion Activities

HR All users tested the following applications successfully: <List specific test executed>

CIRS PIMS, Etc.



Appendix A: Disaster Recovery Applications Testing – Campus Cycles

1. Campuses have been split into two groups for annual Disaster Recovery Applications testing:

a. Spring testing cycle (April/May)

Bakersfield

Chancellor’s Office

Chico

East Bay

Fullerton

Humboldt

Long Beach

Northridge

San Bernardino

San Luis Obispo

San Marcos

Sonoma

b. Fall testing cycle (October):

Channel Islands

Dominguez Hills

Fresno

Los Angeles

Maritime Academy

Monterey Bay

Pomona

Sacramento

San Diego

San Francisco

San Jose

Stanislaus



Appendix B: Frequently Asked Questions (FAQ’S) 1. Can our campus test on another date?

No, the dates for testing are provided by OTech, and the Disaster Recovery site is only active during the designated test dates.

2. What happens if a tester is unavailable to test during the specified testing date?

Have the tester run the test as soon as he/she is able to, within the specified testing period. If the tester is unable to, please contact HR Data Operations to discuss other potential options.

3. Do all testers need to have the shortcut set up on their computers? Yes, all test users need to set up a separate shortcut on their desktop computers. We strongly recommend that this is done before the testing date so that it’s ready to run on the testing date. Doing this in advance will also allow for time to resolve any issues with the shortcut set up prior to the testing date. It is also strongly recommended that users place this testing shortcut away from the real shortcut link for the actual program, so that users do not mistaken the two shortcuts.

4. If the shortcut setup is successful, what should testers see? Prior to the testing date, testers should see a blank screen. When testing is active, testers should see a regular screen similar to the actual screen that campuses use.

5. When running the test, what type of data will testers see? What the data testers will see looks very similar to what users will see normally. However, what testers will key in will not generate a transaction in the production system. No validation is necessary. This is just a test.

6. What do I do if I encounter a problem with an application during testing?

Report any applications or functions that do not work as expected to the HR Data Operations unit immediately.

7. What happens if we do not resolve a problem during the testing period? HR Data Operations will work with the campus, OTech, and the SCO to provide a resolution to the problem. If the problem is not resolved before the Disaster Recovery site shuts down, then it will be readdressed during the next testing cycle.


ATTACHMENT B

Campus Disaster Recovery Testers Form.docx Revision date September 2015

California State University, HR Data Operations Campus Disaster Recovery Applications Testers

SCO Mainframe Applications

Userid Name Phone Number Email C

IRS

PIM

S

HIS

T

KE

YM

PIP

MP

C

VIE

W

PR

INT

FT

P

User Information – Complete information about testers.

Userid Enter the Userid of the tester. Required Enter Coordinator info in first line

Employee Name: Enter the employee’s first name and last name Required

Phone Number Enter the employee’s direct phone number. Required

Email Enter the employee’s email address. Required

SCO Mainframe Applications

Enter an X on the application the tester will test One item must be checked

Enter an X if Printing or FTP will be tested for application testing


ATTACHMENT C

Last Revised: 9/16/2014 Page 1 of 3

Creating a Passport Shortcut to the Disaster Recovery System

You will need to create a new Passport session shortcut to Otech’s Disaster Recovery System. Assuming you set the connection up in advance of the test date, you will get a black screen.

Note: If you are not using Passport, then the settings described in this document should be usable in whatever terminal emulator you use at your campus.

1) Launch the Passport application 2) From the main menu select ‘File’ then ‘New’. This will start the New Session Wizard:

It should default to TN3270 and Display Session, if it does not make those selections now.

Click ‘Next’.

3) Enter in the host name as ‘sy5dr.state.ca.gov’, and port 2323. The other selections should be set up by default as shown below, if not then make any appropriate changes to your set up so it matches the screen below.

Click ‘Next’


ATTACHMENT C


4) Check the box ‘Enable Secure Connection’. ‘SSL/TLS Security’ should be selected by default. All other options can be accepted by default.

Select ‘Next’.

5) Confirm that the settings are correct.

Select ‘Finish’.

This will launch Passport and the application will try to connect to the Disaster Recovery system. However, the system will not be active for connection until the test date, so you should get a blank screen.


ATTACHMENT C


6) From the main screen Select ‘File’, then ‘Save As’. Save the session file to your desktop and name it ‘Disaster Recovery System’. It would be advisable to move the desktop icon away from your normal passport icon to prevent accidental use of the Disaster recovery system.

On the testing date you will be able to launch this short cut and it will connect to the Disaster Recovery System and display a log on screen as normal.

Tip: Some users copied the connection shortcut from a user that had connected successfully to the DR site in the past. The settings are the same, and no user credentials are used in the Emulator settings.

Creating the print session

Telnet print sessions need to be configured to point to the same IP address as telnet terminal sessions connect to – SY5DR. 134.187.90.49 or sy5dr.state.ca.gov. I would suggest creating a separate set of telnet sessions for the users for DR and change the colors on the terminal emulator settings to make it obvious where they are (not helpful for printers, but that’s ok).

Tip: Make a copy of your current Print Session, and rename it ‘DR Print Session’. Open it up and adjust the settings so that it points to the DR Server.

Setting up the FTP connection

Setting up the FTP account will differ from campus to campus as each one uses the FTP Client of its choice. The settings for the DR site will be the same except of the address of the site itself, the DR Site is:

FTP Address: 134.187.90.49 [SY5DR.STATE.CA.GOV]

Logon credentials and port settings will be the same as your regular connection.

TECHNICAL LETTER HR/EHDB 2015-03 ATTACHMENT D

Revised September 22, 2015

OTech Disaster Recovery (DR)

Test Script The script is meant to guide the test and documents the processes, procedures, chronology, and expected results of testing tasks. The “Actual Result” column is meant to be filled in after the test is completed and used for the Test Results Report and Improvement Plan.

TEST SCRIPT RESULTS

Action # Process Steps (Action Item) Expected Actual

CIRS

At the SCO Menu, PF2 key will access the TSO sign-on screen for your userid.

Logon to CIRS

Edit Member Select and edit one of your FOCUS

reports.

Editing functions works

Create new member F2 to create new member Put in a single comment line F3 to save and exit

Create new member

Print Type (P) on the test member you just

created

Print member

Testing Compendium Reports Navigate to the Compendium Reports menu at the top of the screen.

Select the F1 (Express) key and enter ‘A17’ Displays reports A17

Type ‘E’ next to one of your reports. Keep file for one day.

Creates customize report



TEST SCRIPT RESULTS


Insert line and type some text. Edit report ‘F3’ to exit

Online Reporting At the Personal Library, ‘F6’ to go to the common library.

Displays Common library

Type ‘O’ (Online Execution) on FOC2500 Displays PS and SAC file selection. Message number of records selected. Holding Lotus file

Type ‘Fin’ Exits Focus. Displays cost Select ‘F11’ (HoldFile). Select ‘1’ PERMLRG. Select ‘2’ Browse Browses file, confirm results F3 to exit Exits file browser

Batch Execution Navigate to common library (S)Submit BASIC01 Job runs F1 (Status) Status ok F10 to display Results Menu’ Select (1) to Edit report Edit a line Edit report F3 to exit Select 3. Download report Follow on screen instructions to download the report.

Report downloads

Extract (F12) Extract (1) EH with the following options: (2)SSN in library member: history, (1)Effective date 760101 to current, (2)Relative

Displays Extract Screen Displays options and Current Selection screen.



TEST SCRIPT RESULTS


‘Enter’ to continue Include A98, Voided, A54. Submit. Displays History member Enter your SSN in the History member, clearing out any others that are there.

F3 Builds EH file F1 Status Check CTH---- Job# look for successful run

Go to the common library and (S)Submit Hstsumry, select (1) your EH file

Job completes successfully

F10 for results and (1) to edit, ‘Find page’ to go to data and review.

Report looks ok

F3 to exit CIRS Goes to SCO Menu PIMS

Press F1 to enter PIMS database (SCO PROD) Takes you to Sign-on screen. Enter User ID/Password

Press Pause/Break (clear) function key Takes you to blank screen where you enter desired section of PIMS/CSUC

Press enter to go to data entry page Takes you to employment history page where transaction may be keyed

Press Shift/Tab to tab to PSN field Moves cursor to PSN field Type employee’s social security number/enter Takes you to Employee Position

Numbers screen/displays positions

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired section/HIST

Type ee’s SSN & position # at HIST line; press enter

Takes you to CSUC/EE History Synopsis page

Type ‘x’ by desired history transaction Takes you to CSUC Employee History/Detail screen to view detail



TEST SCRIPT RESULTS


Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired section/RST

Type ee’s SSN & position # at RST line; press enter

Takes you to Retirement System Transaction screen to view ret. data

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired section/EAR

Type ee’s SSN at EAR line; press enter Takes you to Employee Action Request-Separation/Disposition screen to view EAR detail

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired section/PPT

Type ee’s SSN & position # at PPT line; press enter

Takes you to Personnel/Payroll Transaction screen (ee’s most current employment history trans detail)

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired section/HIST

Type ee’s SSN & zeros under position field (13)

Takes you to CSUC Employee History/Synopsis screen and displays ee’s EAR history/detail

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired database

Key Transaction Type ‘CSUC’ at blank screen (top left corner) Takes you to employment history

page where transaction may be entered

Type PSD File Reference # (campus ID/Julian date combo) – (9-digits); tab to SSA#; Position#; Transaction Code; Document #

Allows you to enter desired data into the mentioned fields

Press Enter Takes you to the Personnel/Payroll Transaction screen to allow data



TEST SCRIPT RESULTS


entry of additional fields Complete data entry; press Pause/Break to clear

Returns you to blank screen where you enter next desired section or logoff

HIST Type ‘HIST’ at blank screen (top left corner) Takes you to Payroll On-Line

Information System page/history inquiry or YTD inquiry

Type ‘x’ next to Payment History Inquiry; enter

Takes you to Payment History Page

Type ee’s SSN & desired Beginning pay period; Ending pay period; enter

Takes you to Payroll History Summary Page with ee pay hist sum.

Type ‘b’ next to desired payment to view detail Displays both tax and deduction details of selected payment

Type ‘d’ next to desired payment to view detail Displays deduction detail only Press Pause/Break function key (twice) Takes you back to the Payroll On-

Line Information System page/hist

Type ‘x’ next to Year To Date Inquiry; enter Takes you to YTD Inquiry Page Type ee’s SSN next to SSN line; tab to Tax Year (xxxx) line and hit functions keys (F2 or F3 or F4)

Takes you to YTD Summary Selection Menu & displays tax detail/summary or totals for selected tax year (F2 = Summary; F3 = Detail; F4 = Totals only)

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired database or logoff

KEYM Type ‘KEYM’ at blank screen (top left corner) Takes you to Operator Commands

screen

At Command line enter ‘ENT’ & at Takes you to the Batch Entry



TEST SCRIPT RESULTS


Application Name line enter ‘UOSPAR’; enter message page (Assigns Batch #) Key ee SPAR information (A98 trans); enter Allows you to enter all SPAR data Click HOME and Type ‘CLO’ at Command prompt; enter

Closes Batch

Type ‘OFF’ on Command line Accepts signoff (007) Press Pause/Break function key (clear) F12 to Sign Off

Returns to blank screen where you enter next desired database or logoff

PIP Type ‘PIP’ at blank screen (top left corner) Takes you to Batch Entry Page to

allow data entry for new batch

Type ‘MIS’ in ACTN field; enter Takes you to Miscellaneous Earnings page where it assigns a Batch ID #

Type PIP batch detail Allows you to key PIP data Press PF5 to save and close batch Allows you to save and close batch

if in balance & Displays message “Batch In Balance”

Verify Batch Totals Transaction count & Gross amt should be as expected (should tie)

Press Pause/Break function key (clear) Returns you to blank screen where you enter next desired database or logoff

MPC Type ‘MPC’ at blank screen (top left corner) Takes you to Master Payroll

Certification System Menu

Type pay period: (mm/yy); Agency: (xxx); & Reporting Unit: (xxx); tab to Certification status or Add AGY/Reporting Unit; enter

Takes you to Master Payroll Certification System Status page based on criteria chosen

Certify chosen department’s payroll (type 3 next to unit)

Certifies that Unit warrants are correct as issued for selected pay period (leave blank to not certify)



TEST SCRIPT RESULTS


Use function keys to navigate the Certification status page

PF3 to Main Menu; PF4 refreshes page; PF7 to previous unit(s); PF8 to next unit(s); Pause/Break key to clear or logoff

VIEW Agency Reconciliation Report

Log into SCO system and navigate to Reports. Have the Agency report for January 2014 available, for comparison to Testing output.

Access/rights should be same as 'production'.

Select Agency Reconciliation Report: Report ID = FC-320-01

Select July 2015 version: Date = 20150702 View results: Select Fund and compare 100% of output from 'pre-test' to 'testing' version. Print results.

Reports should be identical to production for same parameters.

Exit. Fund Reconciliation Report Log into SCO system and navigate to Reports. Have the Fund reports for July 2015 available, for comparison to Testing output.


Select Fund Reconciliation Report: Report ID = FC-320-35

Select July 2015 version: Date = 20150702 Select Agency View results: Locate Fund 0576-053 and compare 100% from 'pre-test' to 'testing' version. Print results.

Reports should be identical to production for same parameters.

Account Balance Inquiry Log into SCO system and navigate to Online Balance/Detail Inquiry screen.


Select Account 1210 (SMIF) as of 07/15/15 for 0576-031. Have a pre-testing screen print or

$1,258,000



TEST SCRIPT RESULTS


Fund report for 0576-031 1210 available, to compare to Testing output. Make a screen print. Able to produce a hardcopy or a

pdf.

Exit. Transaction Detail Inquiry Log into SCO system and navigate to Online Balance/Detail Inquiry screen.


Key in '00000520000' in Acct: field. Have pre-testing Screen Print or Agency report available.

Exit.

SCO Journal Entry Report Log into SCO system and navigate to the Reports menu and then to Journal Entries.

Request SCO JE SMIFI00140 dated Jan 15, 2015. (SMIF Interest-CA Memorial Scholarship). Locate 0564-$4909.12 & 3033-$12.53. Have pre-testing printout of SCO JE SMIFI00140 dated 1/15/15 available.

Request SCO JE 0009332 dated 9-15-2015. (Transfer Cash to/from Funds per Agency request). Go to testing version of Agency report and check if JE transaction appears for the same amount. Have pre-testing Agency report available.

$1,448.00

Exit. Account Balance Inquiry Log into SCO system and navigate to Online Balance/Detail Inquiry screen.

Compare balances in 0576-310 accounts to



TEST SCRIPT RESULTS


Cash Balances in 1140 account. Have pre-testing screen prints or Agency & Fund reports available.

1140 $476.81 07/01/2015

Request ACL Account Detail for Trust Fund [0948] as of 09/21/15 for Long Beach [Agency 6740]. Have pre-testing screen prints available.

0948: $20,896,690.82

Request ACL Account Detail for closed fund 575-015 Sacramento Union [Prior Year].

The Budget Should be $0

FTP CSU SCO Interface Testing – Benefits Trans

Aka ABS System: Vision, Life AD&D, LTD CMS/Oracle/PeopleSoft Script: Run process in Final Mode to create benefits Extract files (navigation below) Main Menu>Benefits>Interface with Providers> CSU SCO Interface Process Create new Run Control Click ‘Add New Value’ tab Enter Run Control Name Click ‘Add’ button Check ‘Final Load’ option (Y/N) Check ‘All’ option Click ‘Run’ button Select Process Name: ‘PSUNX’ Click ‘OK’ button Click ‘Process Monitor’ Click the appropriate link for the ‘Process Name’: CSUBAS05



TEST SCRIPT RESULTS


Navigate to the ‘.txt’ files Verify that correct transactions were created Transaction files should be ready for electronic Transfer to the SCO (FTP)

Finished Send email to Gene when done testing. [email protected]

* Other applications used by your campus, i.e. PIMS, HIST, KEYM, PIP, MPC, IDLS, VIEW, etc.

These are mainframe applications that are utilized at the campus level, and exact procedures may vary by user and campus.

Please keep in mind that the HR Data Operations team does not have access to, nor utilize these additional applications.

TECHNICAL LETTERHR/EHDB 2015-03

ATTACHMENT E

Campus

Assigned Testing

Period

(Spring/Fall)

Name Phone Number Email

Bakersfield Spring Mark Murie 661‐654‐6918 [email protected]

Chancellor’s Office Spring Angeline Raju 562‐951‐4412 [email protected]

Channel Islands Fall Anna Pavin 805‐437‐8425 [email protected] Islands Fall Diana Enos 805‐437‐8426 [email protected] Spring Rebecca Cagle 530‐898‐5435 [email protected] Spring Doug Wilson 530‐898‐5431 [email protected] Spring Alison Christensen 530‐898‐5476 [email protected] Hills Fall Adria Edwards 310‐243‐2408 [email protected] Bay Spring Tony Tijero 510‐885‐3360 [email protected] Fall Wes Scheibly 559‐278‐4763 [email protected] Fall Brittany Schroeder 559‐278‐2261 [email protected] Spring Blanca Rodriguez 657‐278‐2099 [email protected] Spring Patty Ambrosini 707‐826‐4915 [email protected] Angeles Fall Elcee Teng 323‐343‐3690 [email protected] Beach Spring Kevin Nguyen 562‐985‐8841 [email protected] Fall Cheri Sims 707‐654‐1138 [email protected] Bay Fall Terryn Ashley 831‐582‐3586 [email protected] Spring Brian Cummins 818‐677‐6510 [email protected] Fall Mary Martinez 909‐869‐5097 [email protected] Fall Darlene Edelman 916‐278‐5597 [email protected] Bernardino Spring Shirley Dorsey 909‐537‐3167 [email protected] Diego Fall Devon Caturay 619‐594‐4658 [email protected] Francisco Fall Ericka Jackson 415‐405‐4366 [email protected] Jose Fall Teri Reuck 408‐924‐1708 [email protected] Marcos Spring Jane Cross 760‐750‐4424 [email protected] Luis Obispo Spring Lori Serna 805‐756‐5867 [email protected] Spring Heather Cain 707‐664‐2983 [email protected] Spring Trisha Torgrimson 707‐664‐2178 [email protected] Fall Julie Marlowe 209‐664‐6755 [email protected] Fall D'Ette Gonzales 209‐664‐3992 [email protected]

Campus Test Coordinators for Disaster Recovery Testing Phase 2 (Applications Testing)

Code: TECHNICAL LETTER HR/EHDB 2015-03Office of the Chancellor 401 Golden Shore, 4th Floor Long...

Documents

Transcript of Code: TECHNICAL LETTER HR/EHDB 2015-03Office of the Chancellor 401 Golden Shore, 4th Floor Long...