data migration

14
June 2009 Data Migration

Upload: keisha

Post on 13-Jan-2016

22 views

Category:

Documents


1 download

DESCRIPTION

Data Migration. June 2009. Data Migration. Defined: - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Data Migration

June 2009

Data Migration

Page 2: Data Migration

Data Migration

• Defined:

– PMIS reporting provides information from PMIS as of the date of conversion into BEACON for agency data and current information for University data. The conversion date was December 1, 2007 for group1 agencies (Governors Office, Cultural Resources, Secretary of State, Labor, OSBM, OSP, OSC, Secretary of State) and March 1, 2008 for the other agencies.

– It is important to note that PMIS Data reports are not current for the agencies.

• Future plans:– History and Action reports will have both PMIS and SAP data

2

Page 3: Data Migration

Types of Reports – All PMIS Data

3

Page 4: Data Migration

Report Descriptions

4

Page 5: Data Migration

Types of Reports – SAP and PMIS Data

5

PMSCH 00000

PMHIS

PMXWARN

PMXGRMNU, option 06

PMHIS

PMHIS

PMADDR

PMPROF

PMHIS

PMHIS

Page 6: Data Migration

6

Types of Reports – SAP and PMIS Data

PMXSTATS

PMPERF

Page 7: Data Migration

Example Report

7

1. Select your org unit using SAP org units

2. Personnel Area can only be used by people with statewide access

3. You can use the matchcode to find the PMIS Dept/Div

4. You can do a search

- Case Sensitive

- Wildcards

5. You can enter the PMIS # without the dashes

i.e. 180000000000902

Page 8: Data Migration

Report “Jump”

8

Page 9: Data Migration

List of “Jump” reports

Main Report

• P0007: PMIS Position History

• P0010: PMIS Employee Grievance Listing by Agency

• P0020: PMIS Agency Actions for Selected Grievance

Jump Report

• P0019: PMIS Budget Detail for Related Action

• P0020: PMIS Agency Actions for Selected Grievance

• P0023: PMIS Comments for Selected Grievance

9

Page 10: Data Migration

Understanding the Data

• PMIS Department /division codes and their descriptions were re-used and re-defined over the years on occasion.

– PMIS did not keep a record of the “old” and “new” values for the department/division name changes as they occurred

– In certain instances, the PMIS PMHIS program was customized to display the old department division name as of the effective date of the change

– The department division descriptions in the BI report reflect the most current description available from PMIS (from the PMDESC transaction’s description).

 

10

Page 11: Data Migration

Understanding the Data cont.

• There are also a small number of action codes that have been re-used and redefined over the years in PMIS.  

– PMIS did not keep a record of the “old” and “new” values on these action description changes as they occurred

– In certain instances, the PMIS PMHIS program was customized to display the old action description as of the effective date of the action.

– The data in the BI employee and position history reports contain the most current description available from PMIS (from the PMACT transaction’s action abbreviated description

11

Page 12: Data Migration

Understanding the Data cont.

• When listing positions, you will see ALL positions that EVER existed in the agency– Same concept applies to employee lists

• If you run a report for your agency’s orgunit  and see position’s or employee’s that do not fall under your org structure, pls report issue to BEST

12

Page 13: Data Migration

How to report issues?

• Call BEST Shared Services and log a ticket. The BEACON BI team will investigate the issue

– NOTE: some agencies prefer issues be reported to a central person in the agency; the central person will log the issues.

13

Page 14: Data Migration

Next Steps

• Go-Live Monday, June 15

• Presentation materials can be found:

14